К основному содержанию
скилл CX Codex

create-code-app — скилл для Claude Code: сборка Power Apps на React и Vite

Скилл create-code-app для Claude Code собирает Power Apps code apps: по заданной задаче создаёт проект на React и Vite и разворачивает его в Power Platform.

MIT ★ 1 167 обновлён 2026-10-29

Установить в Claude Code · Через маркетплейс плагинов Все способы и платформы ↓
/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skills
Открыть на GitHub

Что делает create-code-app

Скилл ведёт агента по чёткому маршруту из десяти шагов: проверка окружения, сбор требований, план, скаффолдинг, инициализация, базовая сборка и деплой, подключение данных, реализация приложения, финальный деплой и сводка. Начинается всё с проверки Node.js: нужна версия 22 или новее. Git желателен, но не обязателен.

Для каркаса используется npx degit microsoft/PowerAppsCodeApps/templates/vite, а не git clone — так шаблон скачивается без истории git. Потом инициализация через pa app init с именем приложения и ID окружения. При первом запуске откроется окно браузера для входа в Microsoft.

Скилл рассчитан на модель opus и умеет пользоваться инструментами Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill, EnterPlanMode, ExitPlanMode. После базового деплоя pa app push в выдаче появляется URL вида https://apps.powerapps.com/play/e/{env-id}/app/{app-id}. Без Node.js 22 скилл остановится сразу — дальше шага проверки дело не пойдёт.

Какие задачи решает

  • собрать каркас Power Apps code app одной командой
  • развернуть React-приложение в Power Platform без ручной настройки
  • подключить Dataverse или Work IQ к приложению
  • прогнать деплой по шагам с проверкой на каждом этапе
  • создать структуру проекта с нуля по шаблону Vite

Примеры запросов агенту

  • Создай приложение для учёта заявок клиентов через /create-code-app
  • Собери Power Apps code app на React для работы с данными из Dataverse
  • Разверни проект в Power Platform и покажи URL готового приложения

Как установить create-code-app

1Через маркетплейс плагинов

/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skills

Команда ставит плагин code-apps-preview целиком, со всеми его скиллами

2Через Skills CLI (Vercel)

npx skills add microsoft/power-platform-skills --skill create-code-app -a claude-code

3Вручную: положить файлы

~/.claude/skills/create-code-app/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/create-code-app/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о create-code-app

Как установить create-code-app в Claude Code?

Сначала подключите маркетплейс: /plugin marketplace add microsoft/power-platform-skills, затем установите плагин: /plugin install code-apps-preview@power-platform-skills.

Что делает create-code-app?

Создаёт Power Apps code apps на React и Vite: проверяет окружение, собирает требования, делает каркас проекта, инициализирует его в Power Platform и деплоит. Подходит для создания новых приложений и развёртывания их в Power Platform.

Что нужно для работы скилла?

Node.js версии 22 или новее. При первом запуске pa app init откроется окно браузера для входа в Microsoft — без этого шага команда не завершится.

Исходный текст

SKILL.md · MIT
---
name: create-code-app
description: Creates Power Apps code apps using React and Vite. Use when building code apps, scaffolding projects, or deploying to Power Platform.
user-invocable: true
allowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill, EnterPlanMode, ExitPlanMode
model: opus
---

**📋 Shared Instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.

**References:**

- [prerequisites-reference.md](./references/prerequisites-reference.md) - Prerequisites and required permissions
- [troubleshooting.md](./references/troubleshooting.md) - Common issues, npm scripts, resources

# Create Power Apps Code App

## Workflow

1. Prerequisites → 2. Gather Requirements → 3. Plan → 4. Scaffold → 5. Initialize → 6. Build & Deploy (baseline) → 7. Add Data Sources → 8. Implement App → 9. Final Build & Deploy → 10. Summary

---

### Step 0: Check Memory Bank

Check for `memory-bank.md` per [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md). Skip completed steps.

### Step 1: Validate Prerequisites

Run prerequisite checks **first** -- no point gathering requirements if the environment isn't ready. See [prerequisites-reference.md](./references/prerequisites-reference.md) for details.

Check Node.js and Git (runs natively in bash):

```bash
node --version   # Must be v22+
git --version    # Optional but recommended
```

- **Missing Node.js**: Report "Install Node.js v22+ from https://nodejs.org/" and STOP.
- **Node.js below v22**: Report "Node.js 22+ is required. Please upgrade or switch with `nvm use 22`." and STOP.
- **Missing Git**: Report "Recommended but optional." Continue if approved.
- **All present**: Report versions and proceed.


### Step 2: Gather Requirements

**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:

1. Confirm the app name and clarify the purpose if needed
2. Ask about data -- focus on **what the app needs to do**, not specific technologies:
   - "What data does your app need to work with?" (e.g., company emails, project tasks, custom business records)
   - "Does your app need to search existing information, manage its own data, or both?"
   - Based on their answers, recommend the best approach:
     - **Store and manage custom business data** (tables, forms, CRUD) → Dataverse (`/add-dataverse`)
     - **Interact with specific services** (send emails, post messages, manage files) → the appropriate connector
     - **Search M365 data or get AI-powered answers** (emails, files, people, company knowledge) → Work IQ (`/add-workiq`)
   - If they mention existing Dataverse tables, SharePoint lists, or connectors by name, use those directly
3. Ask about UI requirements: key screens, layout, interactions, theme preference
4. Ask any clarifying questions now -- resolve all ambiguity before entering plan mode

### Step 3: Plan

1. Enter plan mode with `EnterPlanMode`
2. Design the full implementation approach:
   - Which `/add-*` skills to run for data sources
   - App architecture: components, pages, state management
   - Feature list with priority order
3. Present plan for approval, include `allowedPrompts` from [prerequisites-reference.md](./references/prerequisites-reference.md)
4. Exit plan mode with `ExitPlanMode` when approved

### Step 4: Scaffold

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.**

```bash
npx degit microsoft/PowerAppsCodeApps/templates/vite {folder} --force
cd {folder}
npm install
```

**Notes:**

- Use `--force` to overwrite if the directory already has files (e.g., `.claude` from a planning session)
- If targeting an existing directory, use `.` as the folder name: `npx degit microsoft/PowerAppsCodeApps/templates/vite . --force`
- If `npx degit` fails (network issues, npm not found), retry once, then ask the user to run manually

Verify: `package.json` exists, `node_modules/` created.

### Step 5: Initialize

> Resolve the CLI first (see [cli-binary.md](${PLUGIN_ROOT}/shared/cli-binary.md)): run as `$PA app init …` (`npx --no-install pa …`), never a bare `pa`. On `power-apps`-only projects, translate to `power-apps init …` (the `init` verb and its `-n`/`-e` flags are unchanged on both binaries).

```bash
pa app init -n '{user-provided-app-name}' -e <environment-id>
```

**Finding the environment ID:** It's the GUID in the make.powerapps.com URL: `https://make.powerapps.com/environments/<env-id>/home`. If you don't pass `-e`, the CLI will prompt for it interactively.

**Authentication:** On first run, a browser window opens for Microsoft sign-in. Complete the login and the command continues. No separate auth setup is needed.

See [preferred-environment.md](${PLUGIN_ROOT}/shared/preferred-environment.md) for environment selection details.

**`pa app init` failure:**

- Non-zero exit: Report the exact output and STOP. Do not continue to Step 6.
- "environmentId not found" or environment validation error: Verify the environment ID is correct and the user has maker permissions in that environment, then retry.
- Example: _"The `pa app 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` after init and verify `environmentId` is set correctly.

### Step 6: Build & Deploy (baseline)

> **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.

```bash
npm run build
```

Verify `dist/` folder created with `index.html` and `assets/`.

> Deploy via the resolved CLI: `$PA app push` on `pa`, or `power-apps push` on `power-apps`-only projects (see [cli-binary.md](${PLUGIN_ROOT}/shared/cli-binary.md)).

```bash
pa app push
```

**Capture app URL** from output: `https://apps.powerapps.com/play/e/{env-id}/app/{app-id}`

**Common deploy errors:** See [troubleshooting.md](./references/troubleshooting.md).

**Create or update `memory-bank.md` in the project root now** -- don't wait until the end. Include:

- Project path, app name, environment ID, app URL
- Completed steps: scaffold, init, baseline deploy
- Data sources planned (from Step 2)

This ensures progress is saved even if the session ends unexpectedly.

### Step 7: Add Data Sources

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`  |
| Search M365 data or get AI-powered answers | `/add-workiq`      |
| 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 8.

### Step 8: Implement App

**This is the core step.** Build the actual app features described in the plan from Step 3.

1. **Review generated services**: Use `Grep` to find methods in generated service files (they can be very large -- see [connector-reference.md](${PLUGIN_ROOT}/shared/connector-reference.md#inspecting-large-generated-files)). Do NOT read entire generated files.
2. **Build components**: Create React components for each screen/feature in the plan
3. **Connect data**: Wire components to generated services (use `*Service.getAll()`, `*Service.create()`, etc.)
4. **Apply theme**: Use the user's theme preference (default: dark theme per development standards)
5. **Iterate with user**: Show progress, ask for feedback, adjust as needed

**Key rules:**

- Use generated services for all data access -- never use fetch/axios directly
- Read [dataverse-reference.md](${PLUGIN_ROOT}/skills/add-dataverse/references/dataverse-reference.md) if working with Dataverse (picklist fields, virtual fields, lookups have critical gotchas)
- Remove unused imports before building (TS6133 strict mode)
- Don't edit files in `src/generated/` unless fixing known issues

### Step 9: Final Build & Deploy

```bash
npm 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.

```bash
pa app push
```

### Step 10: Summary

Provide:

- App name, environment, app URL, project location
- What was built: features, data sources, components
- Next steps: how to iterate (`npm run build && pa app push`), how to add more data sources
- Suggest what else the app could do:
  - `/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-workiq` -- search M365 data or get AI-powered answers about company info
  - `/add-connector` -- connect to any other service
- Manage at https://make.powerapps.com/environments/<environment-id>/home

### Update Memory Bank

Update the memory bank (created in Step 6) with final state:

- All completed steps (scaffold, data sources, implementation, deploy)
- Features implemented and components created
- Data sources connected
- Suggested next steps

---

## Example Walkthroughs

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.

---

### Example 1: Create a Task Tracker App with Dataverse

**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):**

```bash
# Step 1: Prerequisites
node --version   # → v22.4.0

# Step 4: Scaffold
npx degit microsoft/PowerAppsCodeApps/templates/vite powerapps-task-tracker-20260302 --force
cd powerapps-task-tracker-20260302
npm install

# Step 5: Initialize (browser login prompt on first run; CLI prompts for env ID if -e omitted)
pa app init -n 'Task Tracker' -e <environment-id>

# Step 6: Baseline deploy (pre-approved as part of scaffold flow)
npm run build
pa app push
# → App URL: https://apps.powerapps.com/play/e/32a51012-.../app/<app-id>

# Step 7: Add Dataverse (via /add-dataverse)
pa app add data-source --connector dataverse --table cr123_task
npm run build   # verify connector — no deploy yet

# Step 9: Final deploy (requires user confirmation)
npm run build
pa app push
```

**Files changed:**

| File                                          | Change                                                |
| --------------------------------------------- | ----------------------------------------------------- |
| `power.config.json`                           | Created by `pa app init` — contains `environmentId` |
| `src/generated/models/Cr123_taskModel.ts`     | Generated by `pa app add data-source`               |
| `src/generated/services/Cr123_taskService.ts` | Generated by `pa app 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
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 && pa app 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`:**

```markdown
# 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>

## Completed Steps

- [x] Step 1: Prerequisites validated
- [x] Step 4: Scaffold (npx degit)
- [x] Step 5: Initialize (pa app init)
- [x] Step 6: Baseline deploy
- [x] Step 7: Add Dataverse (cr123_task)
- [x] Step 8: Implement app (TaskList, AddTaskForm)
- [x] Step 9: 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
```

---

### Example 2: Add SharePoint Connector to an Existing App

**User request:**

> "My app already exists. Add SharePoint so I can read items from a list called 'Project Milestones'."

**Commands run (in order):**

```bash
# Step 6: Get connection ID (via /list-connections)
pa connection list
# → ConnectionId: conn-sp-xyz789  (SharePoint Online)

# Step 7: Discover sites
pa connector list-datasets --connector sharepointonline -c conn-sp-xyz789
# → https://contoso.sharepoint.com/sites/Projects

# Step 8: Discover tables
pa connector list-tables --connector sharepointonline -c conn-sp-xyz789 -d 'https://contoso.sharepoint.com/sites/Projects'
# → Project Milestones, Documents, Team Wiki

# Step 9: Add connector
pa app add data-source --connector sharepointonline -c conn-sp-xyz789 -d 'https://contoso.sharepoint.com/sites/Projects' --table '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.
```

© Microsoft · MIT · microsoft/power-platform-skills

Похожие скиллы

Все скиллы по теме «Настройка агента: память, контекст, субагенты» →
power-apps-code-app-scaffold официальный github Скилл power-apps-code-app-scaffold создаёт каркас Power Apps Code App с React и TypeScript. Подходит для старта проекта с коннектором Power Platform. CX Codex +1 8 700установок power-apps-code-apps официальный github Задаёт стандарты стека React, TypeScript и Vite для Power Apps Code Apps. Направляет Copilot при работе с Power Platform SDK, вызовах коннекторов и встраивании Power BI. CX Codex +1 ★ 41 430звёзд репо pixijs-create pixijs Скилл pixijs-create ведёт агента через создание нового проекта PixiJS v8 или подключение библиотеки к уже существующему: шаблоны, пакетные менеджеры, настройка TypeScript. CX Codex +1 6 900установок create-slack-app slackapi Скилл create-slack-app для Claude Code помогает создать Slack-приложение или агента на Bolt. Он проходит настройку CLI, авторизацию и подготовку проекта для запуска. CX Codex +1 1 300установок remotion-create remotion-dev Скилл remotion-create для Claude Code и Codex разворачивает проект Remotion с нуля. Инициализирует репозиторий через npx create-video и готовит окружение к вёрстке видео на React. CX Codex +1 375 000установок create-app SethGammon Скилл create-app для Claude Code и Codex автоматизирует создание приложений по текстовому описанию. Он делит задачу на пять уровней и ведёт разработку через PRD, архитектуру и верификацию. CX Codex +1 ★ 937звёзд репо

Из того же набора157

Весь набор →
setup-app-insights Скилл setup-app-insights для настройки Application Insights в мобильном приложении Power Apps. Включает телеметрию на существующий ресурс Azure, меняет или отключает её. CX Codex +1 ★ 1 167звёзд репо build-ios-binary Скилл build-ios-binary собирает iOS-модуль контрола PAM в плоский device-slice .framework для бандла .ppmplugin. Нужен Mac с Xcode, сборка идёт из одноразовой копии исходников. CX Codex +1 ★ 1 167звёзд репо add-connector Скилл add-connector добавляет коннекторы Power Platform в мобильные приложения на Expo и React Native, если для них нет отдельного специализированного скилла. CX Codex +1 ★ 1 167звёзд репо force-link-environment Скилл force-link-environment для Claude Code переносит среду Power Platform Pipelines на другой хост. Он запускается при ошибке связи с прежним хостом или по запросу сменить хост. CX Codex +1 ★ 1 167звёзд репо add-table-to-offline-profile Скилл add-table-to-offline-profile для Claude Code подключает одну таблицу Dataverse к настроенному Mobile Offline Profile. Запускается после добавления новой сущности. CX Codex +1 ★ 1 167звёзд репо security-review Скилл security-review проводит проверку безопасности сайта Power Pages и собирает результаты в HTML-отчёт. Выберите проверку локальных файлов, готовности к публикации или развёрнутого сайта. CX Codex +1 ★ 1 167звёзд репо genpage-edit-planner Субагент genpage-edit-planner для редактирования уже созданных обобщающих страниц в Power Apps. Анализирует текущую реализацию, сравнивает её с вашим запросом и предлагает план изменений — оркестратор согласует его с вами перед применением. CX Codex ★ 1 167звёзд репо manage-firewall Скилл manage-firewall проверяет и настраивает WAF для сайтов Power Pages. Помогает включить защиту, ограничить доступ по странам или IP и настроить лимиты запросов. CX Codex +1 ★ 1 167звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой