power-platform

Plugin power-platform from marketplace ravenclaude in mcorbett51090/RavenClaude. Commands read from the repo's manifest — today.

Skills (24)

• alm-pipeline-design

  Design end-to-end ALM pipelines for Power Platform solutions — pac CLI primitives, Azure DevOps multi-stage pipelines, source-control unpacked solutions, env-var + connection-reference promotion across DEV → TEST → UAT → PROD, managed-vs-unmanaged discipline. Used by `solution-alm-engineer` (primary

• canvas-app-performance

  Diagnose and fix Power Fx canvas app performance — delegation as a P1 design constraint, lazy-load patterns, Concurrent() vs sequential, ClearCollect vs collection growth, OnStart vs OnVisible, screen-transition cost, control-count budgets per screen, and the connector-call audit via Monitor. Used b

• code-review

  Deep code audit that finds dead wiring, silent failures, unfinished features, placeholder stubs, bloated files, and unnecessary complexity. Produces an actionable report with file:line references grouped by severity. Think of it as a senior dev doing a thorough PR review of the entire codebase. Trig

• copilot-studio-bot-design

  Design Copilot Studio bots — topic vs generative-answers boundaries, knowledge-source hygiene, trigger-phrase design, slot-filling patterns, escalation-to-human criteria, AI Builder vs prompt-flow vs direct Azure OpenAI decisions, and the test-set discipline that catches regressions on every authori

• dataverse-payload-preflight

  Validate a Dataverse create/update payload against LIVE entity metadata in ONE pass — before you POST/PATCH — so you never fix-one-field-and-retrigger. Catches nonexistent columns, invalid option-set values, malformed/missing lookup binds, missing required fields, and the owner-not-provided (SPN-cre

• dataverse-plugins

  Use when developing, registering, or deploying Dataverse plugins (C# server-side extensions). Covers the IPlugin interface, execution pipeline stages, entity images, common patterns (auto-numbering, cascading updates, validation), and registration/deployment. Triggers on: "plugin", "server-side logi

• dataverse-web-api

  Use when programmatically creating, modifying, or querying Dataverse schema and metadata via the Web API (OData v4.0). Covers table/column/relationship definitions, solution ALM, form and view XML construction, app module composition, global option sets, business rules, Custom API registration, and

• dataverse-web-resources

  Use when creating, deploying, or managing Dataverse web resources for model-driven apps. Covers JavaScript form scripts (OnLoad, OnSave, OnChange events), HTML dashboard pages, CSS styling, image resources, navigation/side panes, ribbon/command bar customization, business process flow client API, an

• dlp-policy-design

  Design tenant Data Loss Prevention policies for Power Platform — business / non-business / blocked classification, environment-scoped vs tenant-wide policies, exemption process, common-connector pitfalls (HTTP, SharePoint, Dataverse, custom connectors), and the "every flow gets re-evaluated on polic

• grounding-protocol

  Reduce confident-but-incorrect "I can't do that" claims by forcing agents to verify capabilities before refusing scope. Mandatory checklist covers skills review, alternate-methods enumeration, team-composition check, and escalation phrasing. Inherited by every Power Platform agent.

• maintainability-review

  Forward-looking maintainability + evolvability review of a Power Platform solution — understandability, modifiability, testability, evolution readiness, ownership. Used before major releases, handoffs, when inheriting an existing solution.

• managed-solution-import

  Hardened pac solution import plus explicit baseline-aware cloud-flow reactivation for SPN-driven CI/CD — preflight, baseline, import, reactivate, verify. Managed imports leave flows Draft when the importing identity lacks connection permission; this reactivates only flows that were Active, splits tr

• pbir-ref-integrity

  Report-wide referential-integrity validator for a PBIR Enhanced report's `definition/` tree. Deterministic, stdlib-only `check_refs.py` that catches DANGLING cross-file references — bookmarks pointing at deleted pages/visuals, `visualInteractions` naming visuals that no longer exist, a `pageOrder` t

• pcf-controls

  Use when building, deploying, or using PowerApps Component Framework (PCF) controls. Covers field controls and dataset controls, React virtual controls, control lifecycle, manifest configuration, solution packaging, and deployment. Triggers on: "pcf", "custom control", "component framework", "datase

• plan-with-team

  Spawns an Agent Team to collaboratively plan Power Platform / Dataverse applications. Three specialists (Data Architect, UX Designer, The Skeptic) debate and refine the plan before any code is written. Falls back to structured single-agent planning if agent teams are not enabled. Triggers on: "plan

• power-apps-code-apps

  Use when building, scaffolding, debugging, or deploying Microsoft Power Apps Code Apps using React, Vue, or TypeScript in VS Code. Handles project initialization via pac CLI, Dataverse and connector data access via the @microsoft/power-apps SDK, power.config.json configuration, Vite build pipelines,

• power-automate

  Veteran-level reference for Power Automate work — expressions, error handling + scopes, child flows, solution-aware flows + connection references, Dataverse triggers, throttling, approvals, performance patterns. Used by `flow-engineer` (primary) and any agent touching flows.

• power-bi

  Veteran-level reference for Power BI — PBIP project structure + git, semantic model design, DAX patterns + performance, deployment pipelines, refresh / gateway troubleshooting, integration with Power Platform solutions / ALM. Used by `power-bi-engineer` (primary).

• power-pages-permissions

  Design table permissions, web roles, and authentication for Power Pages — anonymous vs authenticated patterns, B2C / Entra-External-ID auth, table-permission scoping (global / contact / account / parental / self), record ownership, and the "row I can see in MDA but not in Pages" debugging playbook.

• record-screen

  Record a Chrome browser tab to video via CLI. Use when the user wants to capture a screen recording of a browser tab. Supports list, start, stop, caption, and status subcommands. No debug mode required — uses a Chrome extension.

• report-visualization-design

  Design a Power BI report/visualization in the Kurt-Buhler / Bas-Dohmen mold — a checklist-driven method: decide the question first, structure the page with the 3-30-300 information-seeking hierarchy, choose the visual by question-type, design headline KPIs with actual/target/gap + pre-attentive colo

• solution-layering-resolution

  Diagnose and resolve Dataverse solution-layering problems — a managed import that "didn't take", an unmanaged Active layer shadowing managed components, wrong ribbon buttons, components that won't delete, stuck _Upgrade holding solutions, uninstall blockers. Read-only diagnosis first (msdyn_componen

• update-model-driven-app

  Use when an agent must PROGRAMMATICALLY UPDATE an existing model-driven Power Apps app (including its custom pages) in a real Power Platform environment — typically reusing a service principal (SPN). Owns the "there has to be a way" question: it splits the update surface (record/config data · the mo

• visual-qa

  AI-powered visual QA testing that walks through an app in the browser, records every action with annotated captions (what was done, what should happen), captures screenshots/GIFs, and sends the evidence to Gemini for automated review. Catches UX misalignments, broken flows, missing states, and edge

Slash commands (8)

• /power-platform:build-canvas-app

  Build a performant canvas app — delegation-first data access (no non-delegable warnings at scale), an OnStart/OnVisible performance budget, named formulas + With() over repeated work, Patch with defaults + IfError, and a clear canvas-vs-model-driven-vs-code-app call.

• /power-platform:build-copilot-studio-agent

  Build a Copilot Studio agent the right way — route topic vs generative deliberately, select and scope grounding sources, and add escalation + guardrails so the agent hands off cleanly and never answers outside its grounding.

• /power-platform:design-dataverse-schema

  Design a Dataverse table/column schema correctly — choice vs lookup vs customer column, alternate keys for upsert, where to enforce logic (business rule vs rollup vs plug-in), avoiding cascade-on-high-volume-child, least-privilege security roles, and field-level security used sparingly.

• /power-platform:harden-environment-governance

  Harden Power Platform tenant governance — default-deny DLP policies, environment strategy + isolation, secure the default environment, managed environments + sharing limits, and licensing/capacity awareness. The power-platform-admin's tenant-safety checklist.

• /power-platform:model-power-bi-dataset

  Model a Power BI semantic model the right way — star schema not a flat table, measures not calculated columns, deliberate storage mode (Import/DirectQuery/Direct Lake), and row-level security tested as the role. Includes DAX-correctness-as-code.

• /power-platform:scaffold-cloud-flow

  Scaffold a Power Automate cloud flow the right way — pick the trigger with trigger conditions (not runtime filters), use connection references + environment variables (never hardcoded), add error handling/retry + concurrency/pagination, and reach for child flows for reuse. Recommends the Dataverse W

• /power-platform:set-up-alm-pipeline

  Set up a Power Platform ALM pipeline — source-control the unpacked solution tree, one build artifact promoted unchanged across dev→test→prod, connection references + environment variables + Key Vault secrets, managed solutions downstream, and a fresh-import smoke test before release.

• /power-platform:write-platform-tests

  Write Power Platform tests that catch real defects — run as the real security context (not admin), isolate and tear down test data, and treat DAX correctness as code. Covers Dataverse logic, app behavior, and BI measures.

Subagents (11)

• copilot-studio-engineer

  Use this agent for Copilot Studio (formerly Power Virtual Agents) bot design and AI Builder integration — topics, generative answers, knowledge sources, AI Builder models, AI Credit budgeting, bot channels, and 'Copilot Studio vs Azure OpenAI' decisions. NOT for general flow work (flow-engineer).

• dataverse-architect

  Use this agent for Dataverse data modeling, security model design, plug-ins, and business rules. Spawn for 'design these tables', 'model this security', 'should this be a plug-in or a flow', 'audit this schema', or 'migrate this from SharePoint/Excel to Dataverse'.

• flow-engineer

  Use for Power Automate work — cloud flows, desktop flows (RPA), custom connectors, triggers, expressions, error handling. Spawn for flow build/review/troubleshooting or "Power Automate vs Logic Apps vs Function App?". NOT for canvas apps (power-fx-engineer) or data modeling (dataverse-architect).

• model-driven-engineer

  Use for model-driven app construction — site maps, app modules, forms, views, dashboards, business process flows, command bar customization, JS web resources, and form scripting via Xrm/formContext APIs. NOT for data modeling (dataverse-architect) or canvas-only Power Fx (power-fx-engineer).

• pcf-developer

  Use for Power Apps Component Framework (PCF) custom controls — TypeScript, manifest, lifecycle, build, package, register. Pro-code lane, when canvas / Custom Pages cannot deliver the required UI. NOT for canvas formulas (power-fx-engineer) or model-driven JS web resources (model-driven-engineer).

• power-bi-engineer

  Use for Power BI semantic models, DAX authoring/review, reports, dataflows, PBIP source control + Azure DevOps git, deployment pipelines, refresh/gateway troubleshooting, and Power BI ALM/CI-CD. NOT for Dataverse schema (dataverse-architect) or general canvas/Power Fx (power-fx-engineer).

• power-fx-engineer

  Use this agent for canvas Power App work — screen architecture, Power Fx formulas, components and component libraries, delegation, performance, theming, accessibility, Test Studio, Monitor.

• power-pages-engineer

  Use this agent for Power Pages (formerly Power Apps Portals) — external-facing sites for anonymous or B2C users. NOT for internal-tenant apps.

• power-platform-admin

  Use this agent for tenant-level Power Platform admin work — environment strategy, managed environments, DLP at tenant + environment scope, CoE Starter Kit, licensing audits, capacity reporting (Dataverse storage, API entitlements), and risk audits.

• power-platform-tester

  Use this agent for Power Platform-specific testing — Power Fx tests in Test Studio, canvas-app Monitor traces, Power Automate flow tests, Dataverse validation, model-driven form/business-rule testing, DAX measure correctness, Power BI VertiPaq diagnostics, and `pac solution check`.

• solution-alm-engineer

  Use this agent for Power Platform Application Lifecycle Management — pac CLI mastery, source control of unpacked solutions, environment variables, connection references, environment strategy at the solution level (dev/test/prod promotion), and ALM pipelines.

MCP servers (1)

• powerbi-editor

  runs: pbix-mcp-server

Hooks (4)

• PreToolUse

  /usr/bin/env -u BASH_ENV -u ENV -u SHELLOPTS -u BASHOPTS -u LD_PRELOAD -u LD_LIBRARY_PATH -u LD_AUDIT -u DYLD_INSERT_LIBRARIES -u DYLD_LIBRARY_PATH -u PYTHONPATH -u PYTHONSTARTUP PATH=/usr/local/bin:/

• PostToolUse

  /usr/bin/env -u BASH_ENV -u ENV -u SHELLOPTS -u BASHOPTS -u LD_PRELOAD -u LD_LIBRARY_PATH -u LD_AUDIT -u DYLD_INSERT_LIBRARIES -u DYLD_LIBRARY_PATH -u PYTHONPATH -u PYTHONSTARTUP PATH=/usr/local/bin:/

• PostToolUse

  /usr/bin/env -u BASH_ENV -u ENV -u SHELLOPTS -u BASHOPTS -u LD_PRELOAD -u LD_LIBRARY_PATH -u LD_AUDIT -u DYLD_INSERT_LIBRARIES -u DYLD_LIBRARY_PATH -u PYTHONPATH -u PYTHONSTARTUP PATH=/usr/local/bin:/

• PostToolUse

  /usr/bin/env -u BASH_ENV -u ENV -u SHELLOPTS -u BASHOPTS -u LD_PRELOAD -u LD_LIBRARY_PATH -u LD_AUDIT -u DYLD_INSERT_LIBRARIES -u DYLD_LIBRARY_PATH -u PYTHONPATH -u PYTHONSTARTUP PATH=/usr/local/bin:/

Similar plugins