claude-power-platform-community

Model-Driven Apps Development. Use when: building Model-Driven Apps, forms, views, business rules, site map, command bar customization, custom pages, embedded Canvas Apps, subgrids, role-based form switching, generative pages.

Power Apps Code Apps Development (React + TypeScript + Vite). Use when: building Code Apps, three-layer architecture, PAC CLI workflow, Zustand state management, TanStack Query, shadcn/ui components, router basename, provider stack, form patterns, Dataverse integration from React.

WCAG 2.2 AA compliance, accessibility patterns, UX design for Power Platform. Use when: building accessible components, reviewing WCAG compliance, designing loading/empty/error states, responsive design, form accessibility, keyboard navigation, screen reader support, color contrast, focus management.

Dataverse Web API reference. Use when: CRUD operations, OData queries, FetchXML, bulk operations, batch requests, metadata operations, Custom APIs, file/image columns, change tracking, solution management via API, schema creation, programmatic builds.

PCF (Power Apps Component Framework) control development. Use when: building PCF controls, ReactControl, dataset controls, manifest patterns, Fluent UI v9 integration, Canvas App deployment, debugging PCF.

Dataverse C# Plugin development. Use when: writing plugins, IPlugin interface, execution pipeline, entity images, shared variables, unit testing with FakeXrmEasy, plugin registration, ITracingService, sandbox limitations.

Power Platform Critic and Quality Reviewer (Razor). Use when: reviewing architecture, reviewing code, code review, accessibility audit, WCAG compliance check, UX review, ALM review, Dataverse schema review, Power Automate review, Canvas App review, security review. Provides severity-rated findings (S1-S4). Trigger when user says "review this", "check this code", "audit", "is this architecture solid", or after any significant implementation is complete.

Power Platform DevOps and Platform Engineer (Parvez). Use when: provisioning environments, setting up service principals, configuring GitHub Actions CI/CD, Azure Key Vault for secrets, Managed Environments configuration, CoE Starter Kit installation, environment strategy, Git integration setup, Pipeline configuration. Trigger when user mentions "CI/CD", "pipeline", "environment setup", "service principal", "Key Vault", "CoE", or "deploy".

Power Platform Builder (Scott). Use when: building any Power Platform component — Code Apps (React/TypeScript), Canvas Apps (Power Fx), Model-Driven Apps (forms/views/business rules), Power Automate flows, PCF controls, Dataverse schema implementation, plugins (C#), web resources (JavaScript), Power Pages, custom connectors, BPFs, dashboards, ALM pipelines. The hands-on builder for everything Power Platform. Trigger when user says "build", "create", "implement", "configure", or "set up" any Power Platform component.

Power Platform Project Manager (Laura). Use when: gathering requirements, defining acceptance criteria, planning work breakdown, orchestrating multi-agent workflows, tracking deliverables. Handles: requirements elicitation, user stories, Definition of Done governance, agent routing, quality checkpoints. Trigger when user says "plan this", "what do we need", "gather requirements", "orchestrate", or starts a new multi-step Power Platform project.

Power Platform Solutions Architect (Sean). Use when: designing solution architecture, Dataverse schema design, data modeling, ALM strategy, app type selection, integration patterns, security model design, environment topology, Code Apps project structure, Architecture Decision Records (ADRs). Trigger when user asks "how should we build this", "what's the right architecture", "design the data model", or needs to choose between Code App/Canvas/Model-Driven.

Power Platform Solution Consultant and UAT Coordinator (Ava). Use when: writing UAT scripts from acceptance criteria, coordinating test cycles, tracking defects, confirming UAT sign-off, bridging requirements and implementation review, demo preparation, user training documentation, change management. Trigger when user says "UAT", "test scripts", "user acceptance", "defect tracking", "demo prep", "training guide", or "sign-off".

AI Builder for Power Platform. Use when: document processing, prediction models, GPT prompt actions in flows, prebuilt models (text recognition, sentiment, entity extraction), custom models, AI Builder in Canvas Apps and Power Automate, licensing.

Application Lifecycle Management for Power Platform. Use when: setting up CI/CD pipelines, GitHub Actions, solution deployment, environment variables, connection references, managed solutions, Power Platform Pipelines, pac solution sync, deployment settings.

Power Platform Solution Architecture. Use when: selecting app type (Code App vs Canvas vs Model-Driven), designing solution structure, environment strategy, integration patterns, security architecture, DLP policies, capacity planning, Architecture Decision Records (ADRs).

Azure OpenAI and AI integration with Power Platform. Use when: Azure OpenAI, AOAI, AI Foundry, GPT, LLM, AI integration, BYOM, bring your own model, AI Builder prompts, structured output, AI architecture decisions, Copilot Studio custom models.

Business Process Flows (BPFs). Use when: creating BPFs, BPF stages, BPF branching, cross-entity BPFs, BPF XAML creation via API, BPF activation, BPF client-side JavaScript, process instance management.

Canvas Apps Development with Power Fx. Use when: building Canvas Apps, Power Fx formulas, delegation patterns, component libraries, responsive Canvas layout, offline capabilities, modern controls, named formulas, Canvas App ALM.

Microsoft Copilot Studio agent building. Use when: creating Copilot agents, multi-agent orchestration, autonomous agents, MCP integration, knowledge sources, generative actions, Agent API for Power Pages, ALM for agents, testing agents.

Custom Connectors for Power Platform. Use when: building custom connectors, OpenAPI definitions, OAuth authentication, API Key auth, triggers (polling/webhook), connector policies, Azure APIM integration, DLP considerations.

Dataverse System Dashboards and Chart Visualizations. Use when: creating dashboards, dashboard FormXML, chart XML, DataDescription XML, PresentationDescription XML, interactive dashboards, dashboard layout, embedding charts in Model-Driven Apps.

Data migration to and within Dataverse. Use when: data migration, data import, bulk load, CSV import, legacy CRM migration, data quality, deduplication, staging tables, KingswaySoft, Azure Data Factory, dataflows, Web API bulk, entity mapping.

Dataverse MCP (Model Context Protocol) Integration. Use when: querying Dataverse data conversationally, Copilot Studio tool integration, schema discovery in constrained environments, live data validation during development.

Dataverse Schema and Data Modeling. Use when: designing tables, columns, relationships, alternate keys, security roles, cascade behaviors, elastic tables, virtual tables, Dataverse search, query patterns (OData/FetchXML), naming conventions.

Power Platform environment strategy and topology. Use when: environment types, developer environments, sandbox, production, environment groups, environment routing, naming conventions, environment provisioning, environment topology, Managed Environments, environment lifecycle, multi-geo, environment variables across environments.

Power Platform governance, DLP policies, Center of Excellence, tenant administration. Use when: DLP, data loss prevention, governance, CoE, Center of Excellence, tenant settings, sharing limits, compliance, audit, data residency, connector classification, maker controls, admin API.

Power Platform integration patterns with Azure services. Use when: Service Bus, Azure Functions, webhook, event-driven, hybrid, on-premises gateway, VNet, integration pattern, Event Grid, Azure Relay, private endpoints, custom connectors to Azure.

Power Platform licensing and cost optimization. Use when: license types, per user, per app, pay-as-you-go, premium, Copilot Studio licensing, Power Automate licensing, AI Builder credits, Copilot Credits, Managed Environments licensing, capacity, API request limits, cost optimization, feature-to-license mapping.

Microsoft 365 integration with Power Platform. Use when: Teams, SharePoint, Graph API, Outlook, Microsoft 365, M365, Copilot connector, Teams tab, Adaptive Cards, SharePoint lists, Graph queries, email templates, calendar integration.

Power Platform observability, telemetry, and monitoring. Use when: Application Insights, App Insights, monitoring, telemetry, observability, alerting, diagnostics, Monitor tool, tracing, plugin traces, form load times, flow telemetry, Automation Center, dashboards, KQL.

Power Platform performance optimization. Use when: performance, slow, optimization, delegation, caching, indexing, query performance, API limits, throttling, virtual scrolling, lazy loading, concurrent, batch operations, form load.

Power Automate Cloud Flows. Use when: designing flows, error handling (scope try/catch), triggers, Dataverse actions, Apply to Each performance, child flows, HTTP connector, expressions, approval flows, Teams Adaptive Cards, desktop flows (RPA).

Power BI Development. Use when: building reports, TMDL semantic models, DAX patterns, PBIR report definitions, Fabric REST API, Direct Lake, incremental refresh, Dataverse as data source, Power BI Embedded in Code Apps, CI/CD for Power BI.

Power Pages (External Portals). Use when: building portals, web roles, table permissions, Liquid templating, entity lists, entity forms, web forms, Microsoft Entra ID B2C authentication, portal JavaScript, site settings, content snippets.

A team of 6 specialized AI agent skills for Power Platform development, with deep expertise in Code Apps (React + TypeScript + Vite), Dataverse, Power Automate, PCF controls, ALM, DevOps, and UAT coordination. Use this skill whenever the user is working on Microsoft Power Platform — including Code Apps, Canvas Apps, Model-Driven Apps, Dataverse schemas, Power Automate flows, PCF components, solution architecture, ALM/CI/CD pipelines, environment provisioning, or UAT coordination. Trigger when the user mentions: Power Platform, Power Apps, Code Apps, Dataverse, Power Automate, PCF, PAC CLI, model-driven app, canvas app, solution architecture, environment variables, connection references, managed solutions, pac code, React + Power Apps, Vite + Power Apps, WCAG compliance for Power Apps, or any Dataverse schema/security design work. Also trigger when the user asks to plan, design, build, review, or deploy anything related to Power Platform — even if they don't explicitly name the platform (e.g., "build a contact

Dataverse Security Model. Use when: designing security roles, column-level security, business units, teams (owner/access/AAD group), record sharing, hierarchy security, minimum viable privileges, security role management via Web API.

Spec-driven development pattern for Power Platform. Use when: planning non-trivial projects, writing master specifications, splitting component specs, defining build order, requirements documents, design documents, specification templates.

Power Apps Test Engine + Playwright. Use when: E2E testing of Canvas Apps, Model-Driven Apps, or Power Pages; automated UI verification; regression testing in CI/CD pipelines; visual QA of deployed solutions.

Power Platform Testing Strategy. Use when: writing unit tests, E2E tests, Vitest/Jest setup, Playwright, Canvas App testing, plugin testing with FakeXrmEasy, Solution Checker, accessibility testing with axe-core, CI/CD test integration.

Dataverse Web Resources (JavaScript/HTML). Use when: writing form scripts, Xrm Client API, formContext patterns, HTML web resources, ribbon/command bar customization, RibbonDiffXml, web resource deployment, event handlers.