# Edit App

Use when the user wants to iterate on an existing generated Power Apps mobile app after...

- Repository: https://github.com/microsoft/power-platform-skills (1098 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/power-platform-skills --skill edit-app -g -a claude-code -y`
Codex: `npx skills add microsoft/power-platform-skills --skill edit-app -g -a codex -y`
Cursor: `npx skills add microsoft/power-platform-skills --skill edit-app -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/power-platform-skills --skill edit-app -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add microsoft/power-platform-skills`

## Description

Use when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update Application Insights configuration, the plan, data model, native capabilities, design, screens, generated app code, and preview without restarting the full project flow. Natural-language triggers include 'the app already exists', 'edit my app', 'change this screen', and 'add a feature to this app'.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.

**Shared instructions: [shared-instructions.md](../../shared/shared-instructions.md)**, read first.

# Edit App (`/edit-app`)

Post-generation editor for an existing mobile app. `native-app-plan.md` remains the source of truth, but the default outcome is a fixed generated app, not a plan-only diff. After the user approves the plan delta, continue into Dataverse/native/design/screen mutations, run verification, update `memory-bank.md`, and regenerate the static preview when UI changed.

Use `--plan-only` only when the user explicitly asks to update planning docs without changing app code. Normal follow-up prompts in Copilot Chat Agent mode should apply the app change end to end.

## Edit documentation protocol

Keep two HTML files current during every edit:

- `<edit-temp-dir>/edit-app-progress.html` shows the live operation checklist.
- `docs/create-app-plan.html` remains the living description of the app.

Both are best-effort documentation. A rendering failure does not authorize a mutation, cancel an
approval gate, or turn a failed verification into success.

### Progress page

As soon as Step 0 resolves `working_dir`, before inferred-plan sync or the first progress write, ask
`app-docs.js` for a namespaced directory inside the user's OS temp directory:

```bash
node "${PLUGIN_ROOT}/scripts/app-docs.js" --working-dir '<working_dir>' temp
```

The rest: https://github.com/microsoft/power-platform-skills/blob/HEAD/plugins/mobile-apps/skills/edit-app/SKILL.md