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.