claude

power-pages

Create and deploy Power Pages sites using modern development approaches. Supports Enhanced-model non-SPA sites using Liquid and Web Templates, plus SPA sites with React, Angular, Vue, or Astro. Adds multilingual localization and safe runtime LTR/RTL switching for React, Vue, and Angular runtime sites; Astro and Angular static localization are temporarily unavailable. Includes ALM orchestration (plan-alm) with a solution-splitting decision tree, per-solution pipelines, Azure Blob asset advisory, manifest schema v2 for multi-solution deployments, and force-link remediation for cross-host pipeline migrations.

1,143 on GitHubby Microsoftv3.1.0MITupdated today
/

Plugin power-pages from marketplace power-platform-skills in microsoft/power-platform-skills. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (40)

  • activate-site

    Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.

  • add-ai-webapi

    Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings,

  • add-cloud-flow

    Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flo

  • add-localization

    Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro P

  • add-sample-data

    Populates Dataverse tables with sample records for testing and demoing a Power Pages site. Use when the user wants to add sample data, seed data, generate test records, or insert demo data into their tables.

  • add-seo

    Adds SEO essentials to a Power Pages SPA site, including robots.txt, sitemap.xml, meta tags, Open Graph tags, and favicon configuration. Use when the user wants to improve search engine optimization or make their site more searchable.

  • add-server-logic

    Creates, edits, and manages Power Pages Server Logic files — server-side JavaScript that runs securely on the Power Pages runtime. Orchestrates the full lifecycle: gathering requirements, fetching documentation, implementing code, configuring site settings, and deploying. Use when the user wants to

  • analyze-performance

    Statically scans the entire local Power Pages codebase for performance anti-patterns — unpaginated Power Pages lists, webpages/web templates used as custom data APIs, FetchXML over-fetching / N+1 / advanced query hints / cache bypassing, unbounded Web API queries, disabled header/footer output cachi

  • audit-permissions

    Audits existing table permissions on a Power Pages site by analyzing them against site code and Dataverse metadata, then GRADES the configuration with deterministic 1–5 scores across 3 security/usability/correctness categories (9 dimensions). Detection is anchored by a recurring-issue catalog so fin

  • author-webpage-content

    Generates and fills the localized HTML body of an existing webpage in a PAC CLI-downloaded non-SPA Power Pages site from a resolved page-content specification. Use whenever a caller has resolved the existing webpage metadata and asks to compose, replace, append, or modify the exact localized `.webpa

  • compare-site-configurations

    Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test

  • configure-env-variables

    Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and gener

  • create-site

    Creates a new Power Pages site from an SPA or non-SPA template, or scaffolds an SPA from scratch using React, Angular, Vue, or Astro. Guides requirements discovery, template selection, provisioning, design, validation, and deployment. Use when the user wants to create, build, use a template for, or

  • create-webroles

    Creates and configures web roles for a Power Pages SPA site. Web roles control access and permissions for site users, including authenticated and anonymous roles. Use when the user wants to create, add, set up, or manage web roles for their site. Also supports PAC-downloaded non-SPA sites with neste

  • deploy-pipeline

    Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pip

  • deploy-site

    Deploys an existing Power Pages site to a Power Pages environment using PAC CLI. Routes SPA sites to the existing build and upload-code-site workflow, and PAC-downloaded non-SPA (classic) sites to an isolated upload workflow with explicit data-model and website-identity checks. Handles tooling verif

  • diagnose-deployment

    Surfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues. Use when asked to: "diagnose deployment", "debug deployment", "deployment failed", "show deployment errors", "fix deployment issues", "sh

  • edit-site

    Plans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in Design Studio. Use for requests involving pages, localized content, navigation, assets, snippets, site markers, Liquid/web templates, page la

  • ensure-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 (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, u

  • exceptional-web-design

    Reviews the design of an existing non-SPA (classic) or SPA Power Pages site - a live URL or a local project folder - and recommends what to change, without modifying anything. Captures up to eight key pages at desktop and mobile, scores them against the plugin's design rubric (first impression, hier

  • export-solution

    Exports a Dataverse solution containing Power Pages site components as a zip file, ready for deployment to another environment. Use when asked to: "export solution", "download solution", "export managed", "export unmanaged", "package for deployment", "create solution zip", "export site package", or

  • force-link-environment

    Force-links a development or target environment to a Power Platform Pipelines host, overriding any existing association with a previous host. Use when creating a deploymentenvironments record fails with "this environment is already associated with another pipelines host", or when intentionally migra

  • import-solution

    Imports a Dataverse solution zip into a target environment, with optional staged import for dependency checking before committing. Use when asked to: "import solution", "install solution", "deploy solution zip", "push solution to environment", "deploy to staging", "deploy to production", or "install

  • integrate-backend

    Analyzes the user's business problem and recommends the right backend integration approach — Web API, AI Web API (generative summaries / grounded search), Server Logic, Cloud Flows, or a combination — for a Power Pages site, then routes to the appropriate specialized skill. Use when the user wants t

  • integrate-webapi

    Integrates Power Pages Web API into a site's frontend code with proper permissions and deployment. Orchestrates the full integration lifecycle: code integration, table permissions setup, and deployment for Dataverse CRUD operations. Also supports PAC-downloaded non-SPA sites by preferring native For

  • manage-firewall

    Inspects and configures the web application firewall (WAF) in front of a Power Pages production site. Lists the current state, recommends enabling protection when it is off, and walks the user through adding, updating, or removing custom rules — IP blocks, country blocks, path blocks, and rate limit

  • manage-headers

    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 and walks the user through fixes. Use when the user wants to review header

  • migrate-bootstrap

    Migrates a non-SPA (classic) Power Pages site from Bootstrap 3 to Bootstrap 5. Downloads the site, runs the pac pages bootstrap-migrate engine, reviews the change report, applies AI-assisted fixes for the residual hierarchy/CSS changes the engine only flags, uploads the migrated site (which auto-ena

  • migrate-webapi-selectall

    Reviews and migrates deprecated wildcard (*) values in Power Pages Web API fields site settings to least-privilege explicit Dataverse columns. Use whenever a user mentions Web API wildcard or select-all remediation, fields settings containing *, data-exposure review, wildcard deprecation readiness,

  • plan-alm

    Creates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments. Gathers your promotion strategy, target environments, and approval requirements upfront, then generates a visual HTML plan document for your review and approval. **plan-alm does not deploy an

  • report-issue

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the power-pages plugin to the GitHub repository.

  • scan-code

    Scans a Power Pages site project for security issues in source code and dependencies. Runs static analysis and dependency scanning, then surfaces findings by category (code patterns, vulnerable packages, secrets, license issues). Use when the user wants to review code for security problems, check fo

  • scan-site

    Runs a security scan on a deployed Power Pages site, fetches the latest scan report, and produces a plain-language summary. Scans the live site's public surface for vulnerabilities and surfaces issues by severity. Use when the user wants to scan, check, test, audit, or assess a published site, find

  • security-review

    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. Use when the user wants a full security review, a release-r

  • setup-auth

    Use when the user asks to "set up authentication", "add login", "add logout", "add sign in", "enable auth", "add role-based access", "add authorization", "protect routes", "configure identity provider", "configure Entra ID", "configure Entra External ID", "configure OpenID Connect", "add OIDC", "set

  • setup-datamodel

    Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal. Supports SPA sites and PAC-downloaded non-SPA sites. Use when the user wants to set up the data model, create database tables, or build the Dataverse schema for their site.

  • setup-pipeline

    Sets up a Power Platform Pipeline for automated Power Pages deployments. Power Platform Pipelines is Microsoft's native CI/CD tool built into the Power Platform — no external infrastructure required. Use when asked to: "set up ci/cd", "create pipeline", "setup pipeline", "set up power platform pipel

  • setup-solution

    Creates a Dataverse publisher and solution, then adds Power Pages site components to the solution for ALM and deployment management. Use when asked to: "create solution", "set up solution", "add to solution", "package site into solution", "create publisher", "solutionize my site", or "set up ALM for

  • telemetry

    Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-pages telemetry or its usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry stat

  • test-site

    Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.

Subagents (6)

  • ai-webapi-integration

    Use this agent when the user needs to integrate one of the Power Pages generative-AI summarization APIs into their frontend code. The agent supports two APIs: 1. Search Summary — `POST /_api/search/v1.0/summary` 2. Data Summarization — `POST /_api/summarization/data/v1.0/<entitySet>(<id>)?$select=..

  • ai-webapi-settings-architect

    Use this agent when the user wants to configure Power Pages generative-AI summarization site settings (search summary, data summarization, case-page Copilot preset), enable the Summarization APIs, or register maker-defined prompts for the `/_api/summarization/data/v1.0/` endpoint. Trigger examples:

  • data-model-architect

    Use this agent when the user needs to design, plan, or analyze a data model for their Power Pages site. Trigger examples: "design a data model", "what tables do I need", "plan my Dataverse schema", "analyze my data requirements", "propose tables for my site", "show me existing tables", "create an ER

  • table-permissions-architect

    Use this agent when the user wants to set up table permissions for their Power Pages site, configure CRUD access for web roles, or define permission scopes. Trigger examples: "set up table permissions", "configure table permissions", "add table permissions", "set up CRUD permissions", "configure web

  • webapi-integration

    Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web a

  • webapi-settings-architect

    Use this agent when the user wants to configure Web API site settings for their Power Pages site, enable Web API access for tables, or specify which columns to expose via the Web API. Trigger examples: "enable web api", "set up web api", "configure web api settings", "add web api access", "enable ap

MCP servers (2)

  • playwright

    runs: node -e const fs=require('node:fs'); const path=require('node:path'); const fail=(message)=>{throw new Error('[Power Pages Playwright MCP] '+message);}; const declaredRoot=process.env.PLUGIN_ROOT||pro

  • microsoft-learn

    connects to: https://learn.microsoft.com/api/mcp

Hooks (3)

  • PreToolUse

    node -e 'process.on(process.argv[3],()=>{process.exitCode=0});const root=process.env.PLUGIN_ROOT||process.env.CLAUDE_PLUGIN_ROOT;if(!root){console.error(process.argv[4]);process.exit(0)}require(requir

  • PostToolUse

    node -e 'const root=process.env.PLUGIN_ROOT||process.env.CLAUDE_PLUGIN_ROOT;if(!root){console.error(process.argv[3]);process.exit(0)}require(require(process.argv[1]).resolve(root,process.argv[2]))' no

  • UserPromptSubmit

    node -e 'process.on(process.argv[3],()=>{process.exitCode=0});const root=process.env.PLUGIN_ROOT||process.env.CLAUDE_PLUGIN_ROOT;if(!root){console.error(process.argv[4]);process.exit(0)}require(requir

View source on GitHub microsoft.github.io

More from microsoft/power-platform-skills

All 11 plugins →

Build and deploy Power Apps code apps for mobile using Expo (React Native), with native device functionality and Power Platform connectors

31 skills · 5 agents · 1 MCP server · hooks

1,143

Build and deploy Power Apps code apps using React, Vite, and Power Platform connectors.

15 skills · 1 agent · hooks

1,143

Build third-party Power Apps Mobile (PAM) controls into a prebuilt .ppmplugin binary (Android DEX + flat iOS .framework + manifest.json) for the wrap runtime. Public tooling only; recommended build entry point /generate-ppmplugin.

13 skills · hooks

1,143

Build, edit, run, and debug Power Automate cloud flows via the FlowAgent MCP server — connection lifecycle, surgical edits, copy across environments, run management, and validated expressions.

11 skills · 2 MCP servers · hooks

1,143

Build Power Apps Canvas Apps using the Canvas Authoring MCP server.

4 skills · 7 agents · 1 MCP server · hooks

1,143

Build model-driven Power Apps end to end: /app-builder authors whole apps (tables, relationships, forms, views, charts, security roles, app + sitemap) from a natural-language intent, and /genpage builds generative pages with specialist agents for planning, entity creation, and parallel code generation. Requires PAC CLI > 2.10.0 and Azure CLI (`az`). See CHANGELOG.md for v1.x -> v2.x migration.

4 skills · 6 agents · 1 MCP server · hooks

1,143

Similar plugins

Turn an idea into a structured project workflow with planning, execution, verification, and handoff.

10 skills

hashgraph-online/awesome-codex-plugins 1,566

wp-studio

claudecodex

Build, design, and manage WordPress sites with WordPress Studio: create local sites with Studio's design workflow, preview them, and publish to WordPress.com.

11 skills · 1 MCP server

Automattic/studio 552

Power Platform from your AI client: build and debug cloud flows, manage connections, run desktop flows (RPA) and work queues, and administer Dataverse, Power Pages, and tenant governance.

10 skills · 1 MCP server

rcb0727/powerplatform-mcp-docs 102

Reviews the Power Pages site(s) inside a Power Platform solution (.zip) against best practices across Security, Performance, Accessibility, Maintainability, Architecture and Reliability, optionally using a browser HAR capture to investigate real performance bottlenecks. Produces a [SolutionName].findings.json with solution, per-site and per-component findings (descriptions, fixes, code/HAR anchors), then opens the hosted PowerCAT OverPage viewer at https://microsoft.github.io/power-cat-skills/PowerCAT-OverPage.html so the user can explore findings overlaid on a live page preview, on the actual code, and on the network waterfall.

1 skill

microsoft/power-cat-skills 70

Maintain power-pages?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins11 plugins