power-pages

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 diagram", "what entities should I use", "map out my database". This agent is read-only — it discovers existing Dataverse tables, analyzes requirements, and proposes a data model with an ER diagram. It does NOT create, modify, or delete any tables.

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 role access", "add permissions for my tables". This agent analyzes the site, discovers tables and web roles, proposes a table permissions plan with a visual HTML plan file, and after user approval creates the table permission YAML files using deterministic scripts.

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 api client", "create a service for the products table", "add data fetching for my table", "hook up the products api". This agent is NOT for configuring permissions or site settings — use the table-permissions-architect and webapi-settings-architect agents for that. This agent is NOT for designing data models — use the data-model-architect agent for that. This agent creates production-ready Web API integration code — a centralized API client, TypeScript types, and a CRUD service layer for a single Dataverse table. Called by the user or main agent.

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 api access for products table", "configure web api fields". This agent analyzes the site, discovers tables and columns, queries Dataverse for exact column LogicalNames, proposes Web API site settings with case-sensitive validated column names, and after user approval creates the site setting YAML files using deterministic scripts.

This skill should be used when the user asks to "activate site", "provision website", "activate a Power Pages website", "activate portal", "provision portal", "turn on my site", "enable website", or wants to activate/provision a Power Pages website in their Power Platform environment via the Power Platform REST API.

This skill should be used when the user asks to "add sample data", "populate tables", "seed data", "add test records", "generate sample records", "insert demo data", "fill tables with data", "create test data", or wants to populate their Dataverse tables with sample records so they can test and demo their Power Pages site.

This skill should be used when the user asks to "add SEO", "add meta tags", "add robots.txt", "add sitemap", "improve SEO", "search engine optimization", "add open graph tags", "add favicon", "make site searchable", or wants to add SEO essentials (robots.txt, sitemap.xml, meta tags) to their Power Pages code site after creating it with /power-pages:create-site.

Use this skill to audit existing table permissions on a Power Pages site. Trigger examples: "audit permissions", "check permissions", "review table permissions", "are my permissions correct", "permission security audit", "verify permissions setup", "check for permission issues", "permission health check". This skill analyzes existing table permissions against the site code and Dataverse metadata, generates an HTML audit report with findings grouped by severity (critical, warning, info, pass), and suggests fixes for any issues found.

This skill should be used when the user asks to "create a power pages site", "build a code site", "scaffold a website", "create a portal", "make a new site", or wants to create a new Power Pages code site (SPA) using React, Angular, Vue, or Astro.

This skill should be used when the user asks to "create web roles", "add web roles", "set up web roles", "add roles", "create roles for my site", "manage web roles", "add authenticated role", "add anonymous role", or wants to create web roles for their Power Pages code site. Web roles control access and permissions for site users.

This skill should be used when the user asks to "deploy to power pages", "upload site", "publish site", "deploy site", "push to power pages", "upload code site", or wants to deploy/upload an existing Power Pages code site to a Power Pages environment using PAC CLI.

This skill should be used when the user asks to "integrate web api", "add web api", "connect to dataverse", "add api integration", "set up web api calls", "integrate api for my tables", "add crud operations", "hook up web api", "add data fetching", "connect frontend to dataverse", or wants to integrate Power Pages Web API into their site's frontend code with proper permissions and deployment. This skill orchestrates the full integration lifecycle: code integration, permissions setup, and deployment.

This skill should be used when the user asks to "set up authentication", "add login", "add logout", "configure Entra ID", "set up Azure AD auth", "add Microsoft login", "enable authentication", "set up sign in", "add role-based access", "add authorization", "protect routes", "add auth to my site", "configure identity provider", or wants to set up authentication (login/logout via Microsoft Entra ID) and role-based authorization for their Power Pages code site.

This skill should be used when the user asks to "create Dataverse tables", "set up the data model", "setup dataverse", "create tables for my site", "setup dataverse schema", "create the database", "build my data model", or wants to create Dataverse tables, columns, and relationships for their Power Pages site based on a data model proposal.

This skill should be used when the user asks to "test my site", "test the site", "run site tests", "check if site is working", "verify site", "smoke test", "test pages", "check api calls", "test web api", "verify deployment works", or wants to test a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification.