К основному содержанию
плагин

power-pages — плагин для Claude Code: что делает и как установить

Плагин Microsoft для Claude с 39 скиллами: каркас сайта Power Pages, локальная правка, деплой, активация и браузерные тесты.

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

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

Что делает power-pages

Плагин ставит в Claude 39 скиллов: 38 вызываются из разговора, один работает как внутренний исполнитель. Вместе они закрывают цикл сайта Power Pages — от каркаса до публичного адреса. SPA собирают на React, Angular, Vue или Astro, non-SPA остаются на Liquid и Web Templates с моделью Enhanced и вёрсткой Bootstrap 5.

Скелет нового сайта берёт /create-site: подтягивает готовый шаблон или чистый каркас фреймворка, импортирует решения, заливает демо-данные и оставляет открытой статус-страницу со ссылкой. Дальше /edit-site правит скачанный non-SPA сайт, /deploy-site выгружает сборку через pac pages upload-code-site, /activate-site заводит запись сайта и выдаёт публичный адрес, /test-site ходит по ссылкам в браузере через встроенный Playwright MCP и пишет отчёт.

Хуки собраны в одном файле hooks/hooks.json: PostToolUse ловит инструмент Skill и запускает валидацию после нужного скилла. Локализация и переключение LTR/RTL работают на runtime-сайтах React, Vue и Angular, а статическая локализация для Astro и Angular недоступна — многоязычный проход на них придётся строить иначе. Заранее нужны Node.js LTS, PAC CLI и Azure CLI: без PAC CLI деплой, активация и модель данных не пойдут.

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

  • поднять каркас сайта на React или Vue для Power Pages
  • переписать скачанный non-SPA портал под свои Liquid-шаблоны
  • выгрузить собранный проект в среду Power Pages
  • прогнать живой сайт по ссылкам в браузере и собрать отчёт об ошибках
  • разложить одно решение на несколько и развести его по пайплайнам

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

  • Создай сайт Power Pages на React для каталога вакансий и покажи превью
  • Выгрузи мой сайт в среду Power Pages через /deploy-site
  • Прогони тесты по https://contoso.powerappsportals.com и покажи отчёт

Как установить power-pages

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

/plugin marketplace add microsoft/power-platform-skills
/plugin install power-pages@power-platform-skills

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

Вопросы о power-pages

Как установить power-pages в Claude Code?

Добавьте маркетплейс командой /plugin marketplace add microsoft/power-platform-skills, затем поставьте плагин: /plugin install power-pages@power-platform-skills.

Что делает power-pages?

Создаёт, правит, деплоит, активирует и тестирует сайты Power Pages из разговора. Отдельные скиллы закрывают модель данных, аутентификацию, локализацию и ALM с пайплайнами.

Что нужно поставить до начала работы?

Node.js LTS, PAC CLI и Azure CLI. Деплой, активация и работа с моделью данных идут через PAC CLI, так что без него эти шаги не выполнятся.

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

power-pages · MIT
# Power Pages Plugin

Create and deploy Power Pages SPA and non-SPA sites. This plugin covers site creation, local
authoring, deployment, data models, authentication, Web API integration, localization, and ALM
through conversational AI skills.

**Supported frameworks**: React, Angular, Vue, Astro (static SPAs)

## Installation

### From the marketplace

```bash
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-pages@power-platform-skills
```

### From a local clone

```bash
copilot --plugin-dir /path/to/power-platform-skills/plugins/power-pages
# or
claude --plugin-dir /path/to/power-platform-skills/plugins/power-pages
```

## Hook behavior

The plugin centralizes Claude Code hook registration in `hooks/hooks.json`.

- `PostToolUse` hooks match the `Skill` tool so validation runs when a tracked Power Pages skill completes.
- Command validators and checklist verification are maintained centrally instead of in per-skill frontmatter.

This keeps hook behavior in one place and avoids relying on skill-frontmatter hook registration.

## Prerequisites

| Prerequisite | Required for | Install |
|---|---|---|
| [Node.js](https://nodejs.org/) (LTS) | All skills | `winget install OpenJS.NodeJS.LTS` |
| [PAC CLI](https://learn.microsoft.com/power-platform/developer/cli/introduction) | Deploy, activate, data model | `dotnet tool install -g Microsoft.PowerApps.CLI.Tool` |
| [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli) | Data model, sample data, activation | `winget install Microsoft.AzureCLI` |

## Skills

The plugin provides 39 skills: 38 user-invocable skills and one model-only worker.
They cover the full lifecycle of a Power Pages site - scaffolding,
non-SPA authoring, deployment, data modeling, backend integration, authentication, localization,
ALM and CI/CD, security review, performance analysis, testing, auditing, and platform migrations. Each user-invocable
skill is invoked conversationally - just describe what you want to do.

### Site scaffolding and deployment

#### `/create-site`

> "Create a Power Pages site with React for a job board"
>
> "Create a site from a Power Pages template"

Starts a complete site from a curated SPA or non-SPA template, or from a fresh SPA framework
scaffold. The combined template browser labels every entry as **SPA** or **Non-SPA**. SPA template
provisioning imports supporting solutions, applies optional seed data, activates the site, and
leaves the shared status page open with an explicit website link. Non-SPA creation provisions an
Enhanced-model Bootstrap 5 site, downloads and validates its Liquid/Web Template baseline, and
offers coordinated local customization.
SPA template import status updates automatically without a pause control.
Its status page uses the catalog description and original image filenames, with a compact SPA badge and no non-SPA preview notice.
Solutions marked `publishChanges` in the template manifest use `pac solution import --publish-changes`; other solutions import without that flag.
The install confirmation warns that PAC's publication step can include other pending customizations in the target environment.
Financial seed rows use an explicitly selected existing active currency with their amounts unchanged.
Declared attachment uploads omit generated file-name fields from record creation, and seed summaries report partial failures explicitly.
The from-scratch path turns your aesthetic, mood, and optional brand (an existing website, or your colors and logo) into a design thesis and a page-by-page narrative, builds the pages and components with a live preview throughout, and then screenshots every page at desktop and mobile widths and refines it against a ten-category design rubric before the accessibility audit.

- Browse curated SPA and non-SPA templates together
- Choose React, Vue, Angular, Astro, or Non-SPA (Liquid + Web Template)
- Suggests the selected Dataverse environment's base language for site content,
  with a silent `en-US` fallback when the environment cannot be queried
- Renders the implementation plan in the selected content language, including
  correct `lang`/`dir` metadata and an RTL-safe layout
- Separates deterministic agent verification from linguistic, cultural, brand,
  and visual checks that require maker review
- Every visible or interactive component is classified for bidirectional
  behavior, with applicable states and desktop/narrow viewports planned
  separately; direction-neutral layouts work with LTR and RTL from the start
- Script-aware fonts, locale-aware formatting, and mixed-direction content safety
- Real images from Unsplash (no placeholders)
- Live browser preview during development
- Git commits at each milestone

#### `/edit-site`

> "Turn this downloaded Event Portal into our developer conference site"

Authors and coordinates local changes for a PAC-downloaded non-SPA site. It plans and verifies
webpages, Liquid/Web Templates, content snippets, native components, assets, and guarded styling
changes without turning the site into an SPA.

- Keeps one approved customization plan and resumable execution state under `docs/edit-site/`
- Uses Design Studio-compatible composition and Bootstrap-aware styling
- New pages update navigation by default unless the user explicitly asks not to
- Preserves local-only boundaries until the user explicitly runs deployment
- Invokes the model-only `author-webpage-content` worker for localized page-body composition

#### `/deploy-site`

> "Deploy my site to Power Pages"

Builds your project and uploads it to your Power Pages environment using `pac pages upload-code-site`. Handles common blockers like JavaScript attachment restrictions.

- Verifies PAC CLI installation and authentication
- Confirms target environment before deploying
- Creates `.powerpages-site` folder with deployment artifacts

#### `/activate-site`

> "Activate my site"

Provisions a website record in your Power Platform environment so your site is accessible at a public URL.

- Generates a subdomain suggestion (you choose the final name)
- Polls provisioning status until the site is live
- Provides the final site URL

#### `/test-site`

> "Test my deployed site at <https://contoso.powerappsportals.com>"

Runtime-tests a deployed, activated site using a real browser (via the bundled Playwright MCP). Crawls discoverable links, verifies pages render, captures network traffic for API calls, and produces a test report.

- Browser-based navigation and page crawling
- Network request verification for Web API / Server Logic / Cloud Flow endpoints
- Console and network error capture
- Screenshots on failure

Create-site and add-localization also run a component-scoped rendered
bidirectional audit against their development preview. It verifies computed
direction, overflow, clipping, focus order, portals/overlays, applicable
states and viewports, and runtime locale round trips. The run report is
validation evidence rather than a second component manifest. Deterministic
errors keep affected locales unavailable. Only usable review-severity
limitations can be enabled after the maker sees the exact impact and evidence;
that approval is recorded in the localization manifest.

#### `/practice-site-check`

> "Show me how a simple Power Pages skill works"

Provides a small, read-only example for learning skill development. It recognizes both SPA sites and PAC-downloaded non-SPA sites, reports their local identity, and checks framework and compiled output details when they apply.

### Non-SPA site authoring

Use `/edit-site` to customize local PAC CLI-downloaded non-SPA
Power Pages sites. The following capabilities are reference workflows, not separate slash commands,
and do not apply to React, Angular, Vue, or Astro SPA sites.

| Capability | Reference |
|---|---|
| Root/localized webpages, routes, parents, template assignments, content shells, and navigation | [Webpages](skills/edit-site/references/webpage-authoring.md) |
| Localized/neutral snippets, translations, Text/HTML values, Liquid, and exact caller migrations | [Content snippets](skills/edit-site/references/content-snippet-authoring.md) |
| Site-served images, CSS, JavaScript, fonts, documents, and adjacent PAC metadata | [Web files](skills/edit-site/references/web-file-authoring.md) |
| Liquid/HTML fragments, inherited layouts, and explicitly requested callers or bindings | [Web templates](skills/edit-site/references/web-template-authoring.md) |
| Page-template metadata, web-template-backed layouts, rewrite templates, and requested page assignments | [Page templates](skills/edit-site/references/page-template-authoring.md) |
| Named webpage bindings, exact-name Liquid lookups, retargeting, and dependency-safe marker changes | [Site markers](skills/edit-site/references/site-marker-authoring.md) |

The [shared authoring contract](skills/edit-site/references/non-spa-site-authoring.md) owns routing,
autonomy, dependency loading, local-only boundaries, and final verification. New pages update
navigation by default unless you explicitly ask not to. Coordinated asset planning retains provenance,
placement, accessibility, secure explicit Web File imports, and direct HTTPS imagery for new-site design.

#### `author-webpage-content`

Model-only worker invoked by `edit-site` or `integrate-webapi` with a resolved page-content
specification, not a direct user command. Use `/edit-site` for page-authoring requests.

Composes or modifies one localized `.webpage.copy.html` file from a resolved page design,
using Design Studio-compatible sections, columns, text, images, buttons, videos, iframes,
Generative AI Search components, Flex Containers, and spacers.

### Data modeling

#### `/setup-datamodel`

> "Create Dataverse tables for my site"

Analyzes your site's requirements and creates Dataverse tables, columns, and relationships via OData API calls.

- Spawns a **Data Model Architect** agent that proposes tables based on your site's code
- Alternatively, you can upload an ER diagram
- Generates a `.datamodel-manifest.json` used by downstream skills
- Visualizes the data model as a Mermaid ER diagram

#### `/add-sample-data`

> "Add sample data to my tables"

Populates your Dataverse tables with realistic, contextually appropriate records.

- Reads table definitions from `.datamodel-manifest.json` or queries OData metadata
- Generates values that match column types and names (emails, dates, currencies, etc.)
- Inserts records in dependency order (parent tables first)

### Backend integration

#### `/integrate-backend`

> "I need to send a confirmation email when someone submits the contact form"

Router skill that analyzes your business problem and recommends the right backend approach — Web API, Server Logic, Cloud Flow, or a combination — then hands off to the specialized skill(s). Use this as the entry point when you're not sure which integration path fits your scenario.

- Generates a visual backend plan (HTML) with the recommended approach and trade-offs
- Routes to `/integrate-webapi`, `/add-server-logic`, or `/add-cloud-flow`
- Supports multi-approach plans (e.g., Web API for CRUD + Cloud Flow for notifications)

#### `/integrate-webapi`

> "Connect my site to the Dataverse tables"

Orchestrates the full Web API integration lifecycle — from analyzing your site's code to identify where data is needed, through generating typed API code for each table, to configuring table permissions and site settings so the APIs work in production.
It processes the first table sequentially because that creates the shared client, then processes remaining tables in parallel.

The skill first scans your codebase to find components using mock data, placeholder fetch calls, or hardcoded arrays, then maps them to your Dataverse tables. It processes each table sequentially, spawning a dedicated **Web API Integration** agent that creates the integration code. After all tables are wired up, a **Table Permissions** agent proposes CRUD permissions and scopes, and a **Web API Settings** agent proposes site settings with case-sensitive validated column names queried directly from Dataverse — or you can upload your own permissions diagram instead.

**What gets created:**

- Shared `powerPagesApi.ts` client with anti-forgery token management, OData URL builder, and exponential backoff retry logic
- TypeScript entity types and domain mappers per table
- CRUD service layer per table using `/_api/` endpoints with dual token headers and `@odata.bind` for lookups
- Framework-specific patterns: React hooks, Vue composables, Angular injectable services
- Table permission YAML files and site setting YAML files with explicit validated column lists

**What gets updated:**

- Existing components are refactored to use real API calls (mock data and placeholder fetches are replaced)
- `.powerpages-site/table-permissions/` and `.powerpages-site/site-settings/` directories are populated for deployment

#### `/add-ai-webapi`

> "Add AI summaries to my site"

Integrates Power Pages generative-AI summarization APIs into a Single Page Application (SPA) site: the **Search Summary API** (`/_api/search/v1.0/summary`) and the **Data Summarization API** (`/_api/summarization/data/v1.0/...`). Data Summarization can be configured for any record-detail or list page; Microsoft documents one ready-made recipe for a Copilot-style summary on a support-case detail page (`incident` table with `$select=description,title` and the portal-comments expand) — that recipe is available as a maker pick, not an automatic recommendation.

The skill scans your code for search pages and record-detail / list pages and proposes which APIs to wire where. For any Data Summarization target that is missing its Web API prerequisites (Layer 1 `Webapi/<table>/*` settings, Layer 2 table permissions, or the shared `powerPagesApi.ts` client), the skill delegates to `/integrate-webapi` in an **AI-only read mode** — read-only permissions, minimal fields list (no primary key, only `_<col>_value` for lookups) — and to `/create-webroles` if no web role exists yet. Once Layer 1/2 is in place, the skill spawns the **AI Web API Integration** agent sequentially per target to create a single summarization service (`fetchSearchSummary`, `fetchDataSummary`) with correct CSRF handling, a framework-idiomatic wrapper, and real UI call sites. Finally, the **AI Web API Settings Architect** is invoked for Layer 3 to propose the `Summarization/Data/Enable` toggle and per-prompt `Summarization/prompt/<identifier>` settings.

**What gets created:**

- `src/services/aiSummaryService.ts` (or extended if it already exists) with raw `fetch` + both required CSRF headers
- Framework-specific wrapper (React hook / Vue composable / Angular service)
- Real call sites in the target page(s) with loading, error, and recommendation-button handling
- `Summarization/Data/Enable` site setting and one `Summarization/prompt/<identifier>` per prompt
- `Webapi/<table>/enabled` / `Webapi/<table>/fields`, read-only table permissions, and the shared `powerPagesApi.ts` client for the summarised tables and every `$expand` target (delegated to `/integrate-webapi`)

#### `/add-server-logic`

> "Move my pricing calculation out of the browser and onto the server"

Creates and manages Power Pages Server Logic — server-side JavaScript that runs securely on the Power Pages runtime. Covers the full lifecycle: gathering requirements, fetching Microsoft Learn docs for reference, implementing the handler, configuring site settings, and deploying.

- Grounded in live Microsoft Learn docs (via the bundled MCP)
- Generates the server-side handler and its deployment metadata
- Wires up the client-side call site in your frontend code
- Handles site-setting flags required to enable Server Logic

#### `/add-cloud-flow`

> "When a user submits an application, kick off my existing approval flow"

Integrates Power Automate cloud flows into a Power Pages site. Discovers flows available in the environment, suggests relevant ones for your intent, identifies scenarios and web roles, creates flow metadata, and generates the client-side code to invoke the flow.

- Lists available cloud flows in the environment
- Handles both new flow registration and adding already-registered flows to additional pages
- Generates metadata files and client-side call-site code
- Configures web role access for the flow

### Security and access

#### `/create-webroles`

> "Create web roles for my site"

Generates web role YAML files in your `.powerpages-site` directory for managing user access.

- Discovers existing roles before creating new ones
- Generates proper UUIDs for each role
- Enforces uniqueness constraints (one anonymous role, one authenticated role)

#### `/setup-auth`

> "Set up authentication for my site"

Adds login/logout functionality and role-based authorization to your site.

- Auth service with anti-forgery token handling
- Login/logout UI component
- Role-based UI patterns (show/hide elements by role)
- Framework-specific implementation (hooks, composables, services)
- **IDP app-registration setup for OIDC providers** (Okta, Auth0, Microsoft Entra External ID, and other OpenID Connect) — reads the provider's own documentation first, then **guides the user through the provider's console** or, **when the provider supports it, configures the app for the user**; either way it wires the client ID, authority, and claims mapping (registration + login) into Power Pages using the platform-default no-secret `code id_token` flow

#### `/audit-permissions`

> "Check my table permissions for security issues"

Audits existing table permissions on a deployed or in-progress site against the site code and local metadata, querying live Dataverse relationship metadata only when a reachable flow has unresolved dependencies. Produces a visual HTML audit report with a verdict, category scores, and suggested fixes.

- Each issue rated **major** or **minor**, with a Safe to go / Needs revision verdict and 1–5 scores for over-exposure, under-exposure, and correctness
- Each major issue labelled permissions-only or caused upstream (data model, site code, or Web API settings)
- Cross-references code usage, web roles, sign-up settings, and Dataverse schema, and suggests a concrete fix for each issue

#### `/scan-site`

> "Scan my production site for vulnerabilities"

Runs a security scan on a deployed Power Pages site, fetches the latest scan report, and produces a plain-language summary of vulnerabilities by severity.

- Scans the live site's public surface for vulnerabilities
- Fetches and explains the latest scan report
- Surfaces issues grouped by severity

#### `/scan-code`

> "Check my source code and dependencies for security issues"

Scans a Power Pages site project's source files and dependencies for security problems — static analysis of the code plus dependency, secret, and license scanning — then surfaces findings in plain language.

- Runs static analysis (opengrep) and dependency/secret/license scanning (trivy)
- Groups findings by category — code patterns, vulnerable packages, secrets, licenses
- Offers an agent-driven review fallback when the scanning tools are not installed

#### `/manage-firewall`

> "Block traffic from a specific country and add a rate limit to /login"

Inspects and configures the web application firewall (WAF) in front of a Power Pages production site. Walks you through enabling protection and managing custom rules.

- Lists current WAF state and recommends enabling protection when off
- Adds, updates, or removes custom rules — IP blocks, country blocks, path blocks, rate limits
- Protects pages from brute-force attempts and bot traffic

#### `/manage-headers`

> "Fix my CSP errors and harden cookie settings"

Inspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related site settings.

- Identifies gaps in browser security headers
- Walks through fixes for CSP, CORS, cookies, and embedding policy
- Updates the corresponding site settings

#### `/security-review`

> "Do a full security review before we ship"

Runs a guided, end-to-end security review of a Power Pages site and consolidates every finding into one HTML report covering source code and dependencies, the live site, browser headers, firewall, authentication, and role-based permissions.

- Orchestrates `/scan-code`, `/scan-site`, `/manage-headers`, `/manage-firewall`, `/audit-permissions`, and auth checks
- Consolidates findings into a single HTML report
- Suitable for release-readiness or live-site monitoring

### ALM and CI/CD

#### `/plan-alm`

> "Plan how to promote this site to staging and production"

Planner skill that creates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments. Gathers your promotion strategy, target environments, and approval requirements, then generates a visual HTML plan for your review and approval. **It does not deploy anything itself** — after you approve the plan, you run the individual ALM skills, which detect the plan and execute the right step in order.

- Detects project state (config, manifests, current environment)
- Branched flow for Power Platform Pipelines or manual export/import
- Generates `docs/alm-plan.html` for review and approval (the recommended execution sequence is the plan of record)
- Recommends the skill sequence to run next — `setup-solution`, `setup-pipeline`/`export-solution`, `deploy-pipeline`/`import-solution` — each of which detects this plan, proceeds, and keeps it updated as it runs

> [!TIP]
> `/plan-alm` is the front door for any ALM intent — run it first to produce the plan. It plans only; you then run the execution skills it recommends. Use it instead of jumping straight to individual ALM skills when you want to deploy to staging, ship to production, or set up CI/CD.

#### `/setup-solution`

> "Package my site into a solution for ALM"

Creates a Dataverse publisher and solution, then adds Power Pages site components to the solution for ALM and deployment management.

- Creates publisher and solution via OData API (with duplicate detection)
- Adds website and web role components via `AddSolutionComponent`
- Writes `.solution-manifest.json` for downstream skills
- Publisher prefix is irreversible — requires explicit confirmation

#### `/export-solution`

> "Export the solution as a zip for deployment"

Exports a Dataverse solution containing Power Pages site components as a zip file, ready for deployment to another environment.

- Choose managed (locked for downstream environments) or unmanaged (editable)
- Triggers `ExportSolutionAsync` and polls until complete
- Bumps the solution version on every export so each zip is strictly increasing
- Verifies the zip contains a valid `Solution.xml`

#### `/import-solution`

> "Import this solution zip into the staging environment"

Imports a Dataverse solution zip into a target environment, with optional staged import for dependency checking before committing.

- Optional `StageSolution` pre-flight to detect missing dependencies
- `ImportSolutionAsync` with polling until complete
- Writes `docs/alm/last-import.json` marker
- Surfaces per-component import results

#### `/setup-pipeline`

> "Set up a Power Platform Pipeline for automated deployments"

Sets up a Power Platform Pipeline for automated Power Pages deployments. Power Platform Pipelines is Microsoft's native CI/CD tool built into the platform — no external infrastructure required.

- Auto-discovers host environment via `RetrieveSetting('DefaultCustomPipelinesHostEnvForTenant')`
- Creates `deploymentenvironments`, `deploymentpipelines`, and `deploymentstages` records
- GitHub Actions and Azure DevOps platforms show coming-soon guidance
- Writes `docs/alm/last-pipeline.json` and `docs/pipeline-setup.md`

#### `/deploy-pipeline`

> "Deploy the site to staging via my pipeline"

Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Validates the package, optionally configures deployment settings, then deploys and polls for completion.

- Pre-flight check on `blockedattachments` to proactively unblock `.js`/`.css` (saves a wasted ~60-min import)
- `ValidatePackageAsync` before deploying surfaces validation issues early
- Optional environment variable / connection reference overrides per stage
- Final consent gate before the deploy actually fires

#### `/ensure-pipelines-host`

> "Make sure my tenant has a Power Platform Pipelines host"

Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI; if no host is bound, provisions a new **Platform Host** (recommended, idempotent) or guides through a **Custom Host** install.

- Detects host state from org-db setting, BAP env metadata, or default-custom-host setting
- Idempotent Platform Host fast-path (~3–5 min)
- Custom Host fast-path or manual PPAC install fallback
- Writes a host-check artifact other ALM skills consume

#### `/force-link-environment`

> "This environment is already linked to another pipelines host — force-link it"

Force-links a development or target environment to a Power Platform Pipelines host, overriding any existing association with a previous host. Calls the documented `ManageEnvironmentStamp` Dataverse action (the API behind the "Force Link" button in the Deployment Pipeline Configuration app).

- Use when you hit "environment is already associated with another pipelines host"
- Required explicit consent gate — destructive to the previous host (makers lose pipeline access)
- Reversible by re-running from the previous host
- Writes `docs/alm/last-force-link.json`

#### `/configure-env-variables`

> "Make these site settings environment-specific so they differ between dev and prod"

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides you through linking site settings via the Power Pages Management app, adds the variables to the solution, and generates a `deployment-settings.json` file with per-stage override values.

- Creates `environmentvariabledefinition` records (String or Secret type)
- Generates `deployment-settings.json` ready for `deploy-pipeline` to consume
- Routes credentials (ClientSecret, ConsumerKey, etc.) to Key Vault-backed secret env vars

#### `/diagnose-deployment`

> "My last deploy failed — figure out why"

Surfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues.

- Re-runs `pac pages upload-code-site` in capture mode to surface upload errors
- Queries recent Dataverse async operation failures
- Pattern matches against `references/deployment-error-catalog.md`
- Offers auto-fixes with explicit per-fix user confirmation

### Polish

#### `/exceptional-web-design`

> "Review the design of https://contoso.powerappsportals.com"
>
> "Why does my site look generic? What should I change?"

Reviews the design of an existing site - a live URL or a local project folder - and tells you what to change, without changing anything.
It captures up to eight key pages at desktop and mobile widths, runs an accessibility audit, and scores the site against the same ten-category design rubric `/create-site` builds to. Pages beyond that are listed in the report so you can ask for them next.
The result is a scorecard plus prioritized recommendations, each naming the page and element, why it matters, and the exact change, with a redesign direction when the site needs more than fixes.

- Works from a URL (pages are discovered from the site's navigation) or from a project folder, which it reads alongside a URL where the site runs - the deployed site or a dev server you start - or on its own for a code-only review
- Runs nothing from your project and changes nothing in it: screenshots go to a temporary folder outside the project, and nothing is installed
- Pages that require sign-in are listed as not reviewed, because the capture cannot sign in

#### `/add-localization`

> "Add French and German to my site"

Adds or extends multilingual localization for React, Vue, and Angular runtime
Power Pages code-site SPAs. Astro and Angular static localization are
temporarily unavailable.

- Detects and preserves existing localization configuration and translations
- Renders and opens a persistent `docs/add-localization-plan.html` in the
  site's current source language before the terminal approval gate
- Validates canonical BCP-47 language tags against the bundled IANA registry
- Centralizes mode availability: React, Vue, and Angular runtime are active;
  Angular static and Astro static remain dormant for future re-enablement
- Generates translations with the agent or creates blank values for manual
  completion
- Resolves direction from each locale's writing script, including languages
  written in multiple scripts
- Audits every added locale independently, classifies the existing components
  and their applicable states/viewports, and regression-tests shared
  direction-sensitive changes without redesigning unrelated branding or
  behavior
- Adds an accessible language selector with fallback and safe runtime LTR/RTL
  switching; runtime React, Vue, and Angular sites use a locale coordinator
- Keeps only proven affected locales unavailable for later remediation while
  preserving previously verified locales, or records explicit approval for
  usable non-blocking limitations
- Revalidates localization resources, bidirectional source rules, and text-expansion risks after
  later UI-modifying skills and again before deployment
- Localizes only the SPA UI; it does not enable Dataverse environment langu...

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

Похожие плагины

Все плагины по теме «Фронтенд и UI» →
pcf-power-pages официальный github Правило pcf-power-pages подсказывает Copilot, как переносить код-компоненты Power Apps в формы сайта Power Pages и какие API там не работают. CX Codex +1 ★ 41 430звёзд репо power-apps-code-apps официальный Awesome Copilot Community Плагин разворачивает каркас проектов Power Apps Code Apps и подключает агента-эксперта по Dataverse и Power Platform. ★ 41 430звёзд репо mcp-power-automate kaael1 MCP-сервер, через который агент читает, проверяет, правит и откатывает облачные потоки Power Automate. Авторизация берётся из вашей открытой сессии Chromium. CX Codex +1 ★ 30звёзд репо experience-ui-bundle-localize forcedotcom Скилл experience-ui-bundle-localize переносит текст из интерфейсов React и Angular в Salesforce Custom Labels и настраивает runtime i18n поверх GraphQL UI API для B2E и B2C проектов. CX Codex +1 2 200установок MCP Dataverse codeurali Сервер подключает ИИ-ассистентов к Microsoft Dataverse для чтения схем, генерации точных OData-запросов и выполнения пакетных операций. Помогает избежать ошибок в структуре таблиц. CX Codex +1 ★ 18звёзд репо catalyst-slate catalystbyzoho Помогает агенту развернуть фронтенд на Catalyst Slate: создать приложение, настроить slate-config.toml и выкатить сборку. Полезен, когда React или Next.js надо хостить на Catalyst. CX Codex +1 1 200установок

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

Весь набор →
power-automate Открывает доступ к облачным потокам Power Automate через автономный сервер FlowAgent. С его помощью правят логику, диагностируют сбои и переносят потоки между средами. ★ 1 167звёзд репо power-apps-mobile-extension Плагин power-apps-mobile-extension помогает спроектировать и собрать нативный контрол Power Apps Mobile в .ppmplugin и создать парный PCF-контрол для Canvas app. ★ 1 167звёзд репо mobile-app Скилл mobile-app для Claude, который собирает мобильное приложение Power Apps на Expo и React Native: план, экраны, нативные функции и коннекторы. ★ 1 167звёзд репо code-apps-preview Плагин code-apps-preview помогает создавать и развёртывать код-приложения Power Apps на базе React и Vite с готовыми коннекторами платформы. ★ 1 167звёзд репо canvas-apps Плагин canvas-apps связывает Claude Code с открытым приложением Power Apps Canvas. Агент сможет создавать и менять экраны, элементы управления и формулы. ★ 1 167звёзд репо mcp-apps Плагин mcp-apps собирает серверный рантайм MCP-инструмента с JSON-регистрацией и HTML-виджет для его результатов, в том числе без CDN. ★ 1 167звёзд репо pcf Сборка, тестирование, деплой и аудит компонентов PCF для Power Apps. Помогает создавать контролы для model-driven и canvas-приложений. ★ 1 167звёзд репо model-apps Плагин model-apps собирает модельные приложения Power Apps и генеративные страницы из описания обычным языком — от таблиц Dataverse до кода на React. ★ 1 167звёзд репо

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

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