studio-transfer

Transfers canvas Power App source between Power Apps Studio and a repo via manual clipboard pastes.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill studio-transfer-rorysullivan1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: studio-transfer
Source: https://github.com/RorySullivan1/powerapp_taskmaster/tree/main/.claude/skills/studio-transfer
Command: npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill studio-transfer-rorysullivan1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving canvas Power App source between Power Apps Studio on a work machine and a Git repo on another machine has no automated channel — no connector, CI, or export path — only a one-way manual clipboard. This Skill provides the discipline and mechanics to make each paste deliberate, small enough to diagnose, and recorded, so the repo stays the authoritative source. ## Core Features & Use Cases - Code-view transfer mechanics: Grounded guidance on View code / Ctrl+C / Ctrl+V, paste-time validation, suffixed-name renames, and browser clipboard permissions for make.powerapps.com. - App-object exception handling: Routes App.OnStart and App.Formulas through the formula bar instead of code view, avoiding the leading-= and collapsed-comment failure modes. - Paste lifecycle discipline: Enforces the authored → audited → landed lifecycle with a paste log recording intended names, Studio suffixes, and outcomes. - Use Case: You authored a new screen in src/Screens/ and need it live in Studio. The Skill tells you to paste it through code view, rename the suffixed control immediately, log the crossing, and verify with a refresh before trusting any failure report. ## Quick Start Ask the assistant to prepare this authored screen YAML for pasting into Power Apps Studio and explain exactly how to land and log it.

Frequently Asked Questions about studio-transfer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I paste Power Fx control YAML into Power Apps Studio?▼

Enable the Power Fx formula bar in app Settings, then use code view: copy the control's YAML and paste with Ctrl+V. Studio validates before creating the control, assigns a suffixed name like Gallery1_1, and you must rename it immediately and log both names.

How do I get App.OnStart into Power Apps Studio?▼

App.OnStart and App.Formulas have no code view, so they go through the formula bar only. Expand the formula bar before pasting, strip the leading = and any // comments, since a collapsed bar flattens multi-line pastes and a leading comment swallows the whole property.

Why did my paste create a control named Gallery1_1?▼

Studio paste always creates a new control and never patches in place, so name collisions get a numeric suffix. Rename the pasted control to the intended name right away and log both names, or later reconciliation fills with unmapped _1 controls.

Can I paste .pa.yaml source files into Power Apps Studio?▼

No. The .pa.yaml files in an exported .msapp are a read-only review artifact, not a paste source. Only the code-view YAML dialect that Studio itself generates can be pasted through code view.

Why does my app render black and squished after pasting App.OnStart?▼

That symptom means App.OnStart set nothing, usually because a leading = caused a syntax error or a collapsed formula bar let an opening // comment swallow the body. Run OnStart, then type gTheme. into a Fill property to check whether IntelliSense offers the members.

Do layout formulas survive pasting controls into Studio?▼

Yes, at control scope: X, Y, Width, and Height formulas keep recomputing after a control paste, and only direct manipulation overwrites them with constants. Whole-screen pastes behave differently — X was observed lost — so prefer auto-layout container children that own no X.