# Create Mobile App

Use when the user wants to start a new Power Apps mobile app (Expo / React Native /...

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

## Install

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

## Description

Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.

## 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](${PLUGIN_ROOT}/shared/shared-instructions.md)**, read first. Covers safety guardrails, memory bank usage, preferred-environment policy, connector-first rule, Windows CLI compat, command-failure handling.

# Create Power Apps Code App (Native)

Top-level orchestrator. Owns the user-visible flow; delegates planning to the `native-app-planner` agent and per-domain mutation to dedicated `/add-*` skills.

For every child skill handoff, pass the invocation-scoped
[app-edit-routing.md](../../shared/references/app-edit-routing.md) context:
`MOBILE_APP_ORCHESTRATING=1`, `orchestrator: create-mobile-app`, the absolute
`working_dir`, current `phase`, and the exact approved scope/answers for
implementation. Forward it through routers and native helpers; do not persist it
or rely on an earlier shell export. The plan exists before the app is fully built,
so children must use this context rather than mistake creation for a standalone
edit. Design/configuration children still own any approval explicitly delegated
to their phase; this marker never skips those gates.

## Workflow

Intent and creation-state checks → prerequisites → requirements (iOS + Android fixed) →
rough plan preview → Gate 1 architecture (native capabilities, connectors,
then data platform) → Gate 2 Dataverse model when selected → Gates 3 and 4
screen graph/specifications → environment and template preparation → app
initialization → design system → conditional Dataverse materialization and
sample data → Mobile Offline Profile offer for Dataverse apps → native
capabilities and connectors → navigation and screens → validation, preview,
and summary.

---

## Fresh-template working-directory mode

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