edit-canvas-app

# Edit a Canvas App Make the following changes to the existing Canvas App: $ARGUMENTS ## Overview This skill uses two paths depending on edit complexity: - **Simple edits** (single control/property changes, formula tweaks) — handled inline - **Complex edits** (multiple screens, new screens, structural changes, new data sources) — orchestrated via specialist agents: `canvas-edit-planner` + parallel `canvas-screen-editor` --- ## Phase 0 — Create App Folder Before syncing or editing, create a subfolder to contain the app's YAML files: 1. Derive a short folder name from `$ARGUMENTS` — extract the app name if present, otherwise use a 2–3 word summary of what is being edited 2. Convert to kebab-case (e.g., "Expense Tracker" → `expense-tracker`) 3. Create the folder using `Bash`: `mkdir -p <folder-name>` 4. Resolve its absolute path — this is the **working directory** for all subsequent phases All file reads, writes, and syncs operate in this folder. --- ## Phase 1 — Sync and Check **Sync the canvas app:** Call the `sync_canvas` MCP tool targeting the working directory. This pulls the current app state from the coauthoring session into local `.pa.yaml` files. Only proceed after `sync_canvas` completes successfully. **Check for meaningful content:** After `sync_canvas` completes, read the synced `.pa.yaml` files and check whether the app has meaningful content. An app is considered **empty** if: - No `.pa.yaml` files were written, or - The only files present con...