powerapps-code-app skill

A GitHub Copilot skill (agent) for extending Power Apps Code Apps conversationally. It drives the full development loop — from discovering project state through adding data sources and flows all the way to local testing and deployment to Power Platform.

What this skill does

Capability	Description
Add Dataverse tables	Runs pac code add-data-source -a dataverse and verifies the generated service/model files
Add connectors	Wires Office 365, SQL, SharePoint, Copilot Studio, and other Power Platform connectors
Add Power Automate flows	Uses npx power-apps add-flow to integrate solution-aware flows with a PowerApps trigger
Run locally	Launches npm run dev and surfaces the Local Play URL with auth reminders
Deploy to Power Platform	Runs npm run build + push via the npm CLI or pac code push

When it triggers

Use this skill when the user wants to:

• Wire data into a code app
• Ask about pac code, npx power-apps, pac connection list, power.config.json, add-data-source, or add-flow
• Test or deploy a code app

Does NOT trigger for: model-driven apps, canvas apps (non-code), or PCF code components — those use different tooling.

Repository layout

SKILL.md                  # Main skill definition and orchestration instructions
agents/
  prereq-doctor.md        # Sub-agent: diagnoses auth/env blockers
  dataverse-wirer.md      # Sub-agent: scaffolds typed hooks + UI for a data source
  deploy-runner.md        # Sub-agent: handles build + push
references/
  01-prereqs.md           # Prerequisites (PAC CLI, npm CLI, auth)
  02-dataverse.md         # Adding Dataverse tables
  03-connectors.md        # Adding Power Platform connectors
  04-flows.md             # Adding Power Automate flows
  05-testing-local.md     # Running the app locally
  06-deploy.md            # Deploying to Power Platform
  07-best-practices.md    # Code best practices (select columns, partial updates, etc.)
  08-cli-cheatsheet.md    # Full CLI command reference
scripts/
  preflight.ps1           # Bootstrap script — emits project state as JSON

CLI quick reference

Operation	Preferred	Fallback
Init project	npx power-apps init	pac code init
Add Dataverse table	pac code add-data-source -a dataverse -t <name>	—
Add connector	pac code add-data-source -a <api> -c <id>	—
Add flow	npx power-apps add-flow --flow-id <id>	—
Run local	npm run dev	—
Push to cloud	npx power-apps push	pac code push

Full reference: references/08-cli-cheatsheet.md

Prerequisites

• Power Platform CLI (pac) — for Dataverse and connector operations
• Node.js + npm — for the npm CLI and local dev server
• @microsoft/power-apps npm package ≥ 1.0.4 (≥ 1.1.1 for flow support)
• An authenticated Power Platform environment (pac auth create)

Run scripts/preflight.ps1 at the start of a session to validate all prerequisites and emit the current project state.

Safety rules

• Read-only operations (listing auth profiles, connections, data sources, reading config files, npm run dev) run without confirmation.
• Mutations (adding/removing data sources or flows, pushing to cloud, writing files under src/) require explicit user confirmation via AskUserQuestion.
• Never edit src/generated/ — these files are regenerated by the CLI. To update a schema, delete and re-add the data source.

Sub-agents

The orchestrator spawns specialized sub-agents for complex phases:

Sub-agent	When fired	File
prereq-doctor	Auth state ambiguous, env mismatch, PAC missing	agents/prereq-doctor.md
dataverse-wirer	After a data source is added and the user wants UI scaffolding	agents/dataverse-wirer.md
deploy-runner	During the deploy phase (build + push)	agents/deploy-runner.md

Related resources

• Power Apps Code Apps documentation
• Power Platform CLI reference
• PowerAppsCodeApps templates