From code-apps-preview
Creates React and Vite code apps for Power Apps. Scaffolds projects, checks prerequisites like Node.js and pac CLI, authenticates, builds, and deploys to Power Platform.
npx claudepluginhub microsoft/power-platform-skills --plugin code-apps-previewThis skill is limited to using the following tools:
**๐ Shared Instructions: [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
Routes to specialized skills for adding Power Apps data sources like Dataverse (business data), SharePoint lists, Teams messages, Excel, OneDrive, and Office 365 based on user goals.
Integrates Power Pages Web API into frontend code sites for Dataverse tables, implementing API clients, CRUD operations, permissions setup, and deployment.
Creates, updates, and deploys Power Apps generative pages for model-driven apps using React 17, TypeScript, Fluent UI V9, and PAC CLI. Useful for building or updating pages in Power Apps.
Share bugs, ideas, or general feedback.
๐ Shared Instructions: shared-instructions.md - Cross-cutting concerns.
References:
Check for memory-bank.md per shared-instructions.md. Skip completed steps.
Run prerequisite checks first -- no point gathering requirements if the environment isn't ready. See prerequisites-reference.md for details.
Check Node.js, the npm CLI package, and Git (runs natively in bash):
node --version # Must be v22+
git --version # Optional but recommended
Check pac CLI via PowerShell โ it's a Windows executable not on the bash PATH:
pwsh -NoProfile -Command "pac" # Used for auth, env selection, code commands
nvm use 22." and STOP.Skip questions the user already answered in their initial instruction.
If the user has not described what they want to build (i.e., /create-code-app was invoked with no arguments or a vague prompt), start with a single open-ended question before asking anything else:
"What would you like to build? Describe it in your own words โ what it does, who uses it, and what problem it solves."
Wait for their answer. Use it to frame all follow-up questions. Do NOT present a multiple-choice list of app types before the user has described their idea.
Once you have their description:
/add-dataverse)EnterPlanMode/add-* skills to run for data sourcesallowedPrompts from prerequisites-reference.mdExitPlanMode when approvedpwsh -NoProfile -Command "pac auth list"
If empty, proceed since the command will use system credentials. If profiles are listed, check which environment they target.
If multiple profiles are listed: Notify the user that using Microsoft tenant credentials requires clearing all profiles first, then run:
pwsh -NoProfile -Command "pac auth clear"
After clearing, there is no need to run auth create. The tool picks up the system login automatically.
pwsh -NoProfile -Command "pac auth list" shows the active auth profile with its environment. Check which environment it targets.
pwsh -NoProfile -Command "pac env list", show up to 10 options, let the user pick, and run pwsh -NoProfile -Command "pac env select --environment <id>".See preferred-environment.md for details.
Critical: Capture the environment ID for Step 7.
Ask the user for a folder name. Default to powerapps-{app-name-slugified}-{timestamp} if they don't have a preference.
IMPORTANT: Use npx degit to download the template. Do NOT use git clone, do NOT manually create files, do NOT download from GitHub UI. degit downloads the template without git history.
npx degit microsoft/PowerAppsCodeApps/templates/vite {folder} --force
cd {folder}
npm install
Notes:
--force to overwrite if the directory already has files (e.g., .claude from a planning session). as the folder name: npx degit microsoft/PowerAppsCodeApps/templates/vite . --forcenpx degit fails (network issues, npm not found), retry once, then ask the user to run manuallyVerify: package.json exists, node_modules/ created.
pwsh -NoProfile -Command "pac code init --displayName '{user-provided-app-name}' -e <environment-id>"
pac code init failure:
-e value.pac code init command failed: [error text]. Please check that environment ID 32a51012-... is correct and that you have maker permissions in that environment."Critical: Read power.config.json and verify environmentId matches Step 4. Update if mismatched (common issue).
Pre-approved: This baseline deploy is part of the scaffold flow and does not require a separate confirmation prompt.
Build and deploy the bare template to verify the pipeline works before adding data sources.
npm run build
Verify dist/ folder created with index.html and assets/.
pwsh -NoProfile -Command "pac code push"
Capture app URL from output: https://apps.powerapps.com/play/e/{env-id}/app/{app-id}
Common deploy errors: See troubleshooting.md.
Create or update memory-bank.md in the project root now -- don't wait until the end. Include:
This ensures progress is saved even if the session ends unexpectedly.
Invoke the /add-* skills identified in the plan (Step 3). Run each in sequence. Pass context as arguments so sub-skills skip redundant questions (project path, connector name, etc.):
| App needs to... | Invoke |
|---|---|
| Store/manage custom business data | /add-dataverse |
| Track work items, bugs, pipelines | /add-azuredevops |
| Send or read Teams messages | /add-teams |
| Read/write Excel spreadsheet data | /add-excel |
| Upload, download, or manage files | /add-onedrive |
| Work with SharePoint lists or docs | /add-sharepoint |
| Send emails, read inbox, manage calendar | /add-office365 |
| Invoke a Copilot Studio agent | /add-mcscopilot |
| Connect to another service | /add-connector |
Each /add-* skill runs npm run build to catch errors. Do NOT deploy yet.
If no data sources needed: Skip to Step 9.
This is the core step. Build the actual app features described in the plan from Step 3.
Grep to find methods in generated service files (they can be very large -- see connector-reference.md). Do NOT read entire generated files.*Service.getAll(), *Service.create(), etc.)Key rules:
src/generated/ unless fixing known issuesnpm run build
Fix any TypeScript errors. Verify dist/ contains the updated app.
Ask the user: "Ready to deploy to [environment name]? This will update the live app." Wait for explicit confirmation before proceeding.
pwsh -NoProfile -Command "pac code push"
Increment version (e.g., v1.0.0 โ v1.1.0) and update version display in the app.
Provide:
npm run build && pac code push), how to add more data sources/add-datasource -- add another data source (describe what you need, and the plugin will recommend the best approach)/add-dataverse -- store and manage custom business data/add-azuredevops -- track work items, bugs, and pipelines/add-teams -- send and read Teams messages/add-sharepoint -- work with SharePoint lists or documents/add-office365 -- send emails, manage calendar/add-connector -- connect to any other serviceUpdate the memory bank (created in Step 7) with final state:
These walkthroughs show the full sequence from user request to final output โ commands run, files changed, and the verbatim summary format the assistant should use.
User request:
"Build me a simple task tracker that stores tasks in Dataverse. I want to add tasks, mark them complete, and see a list."
Commands run (in order):
# Step 1: Prerequisites
node --version # โ v22.4.0
pwsh -NoProfile -Command "pac" # verify installed
# Step 4: Auth
pwsh -NoProfile -Command "pac auth list" # โ verify active environment
# Step 5: Scaffold
npx degit microsoft/PowerAppsCodeApps/templates/vite powerapps-task-tracker-20260302 --force
cd powerapps-task-tracker-20260302
npm install
# Step 6: Initialize
pwsh -NoProfile -Command "pac code init --displayName 'Task Tracker' -e <environment-id>"
# Step 7: Baseline deploy (pre-approved as part of scaffold flow)
npm run build
pwsh -NoProfile -Command "pac code push"
# โ App URL: https://apps.powerapps.com/play/e/32a51012-.../app/<app-id>
# Step 8: Add Dataverse (via /add-dataverse)
pwsh -NoProfile -Command "pac code add-data-source -a dataverse -t cr123_task"
npm run build # verify connector โ no deploy yet
# Step 10: Final deploy (requires user confirmation)
npm run build
pwsh -NoProfile -Command "pac code push"
Files changed:
| File | Change |
|---|---|
power.config.json | Created by pac code init โ contains environmentId |
src/generated/models/Cr123_taskModel.ts | Generated by pac code add-data-source |
src/generated/services/Cr123_taskService.ts | Generated by pac code add-data-source |
src/components/TaskList.tsx | Created โ renders task list with status filter |
src/components/AddTaskForm.tsx | Created โ form to add new tasks |
src/App.tsx | Updated โ wires components to Cr123_taskService |
memory-bank.md | Created in Step 7, updated in Step 11 |
Final assistant summary (verbatim format):
Task Tracker is live.
App: Task Tracker v1.0.0
Environment: <your-environment-name> (<environment-id>)
URL: https://apps.powerapps.com/play/e/<environment-id>/app/<app-id>
Project: ~/powerapps-task-tracker-20260302/
What was built:
- Task list view with Active / Completed filter
- Add task form (title, description, due date)
- Mark complete / delete actions
- Dataverse table `cr123_task` (Title, Description, DueDate, IsComplete)
To redeploy: npm run build && pac code push (from the project folder)
What you can add next:
- /add-teams โ post task updates to a Teams channel
- /add-office365 โ send email notifications on completion
What to record in memory-bank.md:
# Task Tracker โ Memory Bank
## Project
- Path: ~/powerapps-task-tracker-20260302/
- App name: Task Tracker
- Environment: <your-environment-name> (<environment-id>)
- App URL: https://apps.powerapps.com/play/e/<environment-id>/app/<app-id>
- Version: v1.0.0
## Completed Steps
- [x] Prerequisites validated
- [x] Scaffold (npx degit)
- [x] Initialize (pac code init)
- [x] Baseline deploy
- [x] Add Dataverse (cr123_task)
- [x] Implement app (TaskList, AddTaskForm)
- [x] Final deploy
## Data Sources
- Dataverse: cr123_task (Title, Description, DueDate, IsComplete)
## Components
- TaskList.tsx โ filtered list, mark complete, delete
- AddTaskForm.tsx โ create new tasks
## Next Steps
- Consider /add-teams for task assignment notifications
User request:
"My app already exists. Add SharePoint so I can read items from a list called 'Project Milestones'."
Commands run (in order):
# Step 6: Get connection ID (via /list-connections)
pwsh -NoProfile -Command "pac connection list"
# โ ConnectionId: conn-sp-xyz789 (SharePoint Online)
# Step 7: Discover sites
pwsh -NoProfile -Command "pac code list-datasets -a sharepointonline -c conn-sp-xyz789"
# โ https://contoso.sharepoint.com/sites/Projects
# Step 8: Discover tables
pwsh -NoProfile -Command "pac code list-tables -a sharepointonline -c conn-sp-xyz789 -d 'https://contoso.sharepoint.com/sites/Projects'"
# โ Project Milestones, Documents, Team Wiki
# Step 9: Add connector
pwsh -NoProfile -Command "pac code add-data-source -a sharepointonline -c conn-sp-xyz789 -d 'https://contoso.sharepoint.com/sites/Projects' -t 'Project Milestones'"
# Step 11: Build to verify
npm run build # โ success
Files changed:
| File | Change |
|---|---|
src/generated/services/SharePointOnlineService.ts | Generated โ contains GetItems, PostItem, etc. |
src/generated/models/SharePointOnlineModel.ts | Generated โ TypeScript interfaces |
.power/schemas/sharepointonline/ | Generated schema files |
memory-bank.md | Updated โ connector recorded |
Final assistant summary (verbatim format):
SharePoint Online connector added.
Connector: SharePoint Online
Site: https://contoso.sharepoint.com/sites/Projects
List: Project Milestones
Build: Passed โ
Usage:
const result = await SharePointOnlineService.GetItems({
dataset: "https://contoso.sharepoint.com/sites/Projects",
table: "Project Milestones"
});
const milestones = result.data?.value || [];
Next: Implement your UI components using the generated service, then run /deploy when ready.