conventions plugin

What's inside conventions

6 parts read from the plugin's own files.

Skills in conventions

1. 
   dataverse-conventionsPowercademy/powercademy-skills

   Apply Powercademy's Dataverse and Power Platform conventions before creating or changing schema - tables, columns, choices, record status, relationships, solutions, publishers - so established judgement is applied and known mistakes are not repeated. Trigger before any Dataverse schema work: "create a table", "add a column", "new choice column", "status field", "statecode", "status reason", "set up a solution", "which publisher", "add to solution", "import failed", "missing dependency", or any Power Platform / Dynamics 365 build or review touching schema, solutions, or ALM packaging - even when nobody says "best practice". Also trigger when a new convention is agreed or a mistake is corrected during Power Platform work, so the lesson gets recorded. Each entry carries its reasoning, so you can tell when it applies and when an exception is justified. If the task creates or changes Dataverse components, trigger. When in doubt, trigger.

   8stars
2. 
   flow-conventionsPowercademy/powercademy-skills

   Apply Powercademy's Power Automate lessons before building, editing or debugging a cloud flow - whichever tool does the building - so known traps are avoided rather than rediscovered. This skill holds the accumulated flow gotchas log: editing flows that already run (renames, child-flow contracts, blast radius, regression checks), designer quirks (255-character descriptions, nesting), expressions, Parse JSON, HTTP and Microsoft Graph permissions, child flow patterns, environment variables and ALM, testing when a dependency is unavailable (mocks, write gates, dry-run guards) and anti-patterns. Trigger alongside any flow work: "build a flow", "edit this flow", "add a step to my flow", "why did my flow fail", "child flow", "Parse JSON", "flow expression", "Graph call from a flow", "test this flow without the real system". It does not build flows itself - apply it, then carry on with the build tool. Also trigger when a flow lesson is learned or a mistake corrected, so it gets recorded. When in doubt, trigger.

   8stars
3. 
   model-driven-uxPowercademy/powercademy-skills

   Apply Powercademy's UX conventions to model-driven apps, forms, command bars, dialogs and custom or generative pages, so apps feel finished and users can act without guessing. Holds the rules for command bar buttons built in the command designer - every button has an icon that says what it does, paired actions get paired icons, no icon reused for different actions on one bar, label, tooltip and accessibility text set - and for focused-task dialogs being modal. Trigger whenever the user is designing or reviewing a model-driven app's look and behaviour: "add a button", "command bar", "command designer", "ribbon", "button icon", "which icon", "Icon is required", "new command", "custom page", "generative page", "dialog", "popup", "modal", "form layout", "make the app look better", "review my app's UX". Also trigger when building commands or pages with Microsoft's tooling, and when a new UX lesson is learned, so it gets recorded. When in doubt, trigger.

   8stars
4. 
   pcf-conventionsPowercademy/powercademy-skills

   Apply Powercademy's PCF judgement before building, deploying or debugging a Power Apps component framework (PCF) code component - whichever tool builds it - starting with whether PCF is even the right tool. Holds the decision gate (out-of-the-box, canvas component or generative page first), the control-type choice (field, dataset, virtual React) and the PCF gotchas log: version bump or the cached bundle keeps rendering, dev push is not ALM, manifest binding, lifecycle traps, the harness is not the real host, the premium-licensing trap, bundle weight. Trigger alongside any PCF work: "build a PCF control", "code component", "custom control", "dataset control", "ControlManifest", "pac pcf push", "my control won't update", "works in the harness but not on the form", "does this make my app premium". It does not build controls - apply it, then carry on with the build tool. Also trigger when a PCF lesson is learned, so it gets recorded. When in doubt, trigger.

   8stars
5. 
   tool-selectionPowercademy/powercademy-skills

   Pick the right tool for each Power Platform task before acting - purpose-built plugin tools and MCP servers first, then the Dataverse SDK, Web API or pac CLI, and browser automation (Playwright) only for what has no API - and never tell the user something can't be done while browser automation could do it. Prevents the two failure modes: driving the maker portal through a browser for work an SDK does in one call (slow, brittle, costly), and refusing work that only the UI can do. Trigger whenever several tools could do the job: "use Playwright", "open the browser", "click through the portal", "is there an API for this", "bulk update records", "load this data", "create these columns", "change this setting", "check it looks right", "why is this so slow", "can you do this", and before saying any Power Platform task is impossible. Also trigger when browser automation is about to be used for data, schema, solution or flow work. When in doubt, trigger.

   8stars
6. 
   writing-skillsPowercademy/powercademy-skills

   This skill holds the Powercademy Skills house standard and the lint-enforced constraints that CI rejects violations of - dual-runtime portability rules, description limits, path conventions, the mechanics quarantine, redaction policy. Reviewing or authoring a marketplace skill without loading it will miss enforced constraints and fail CI. Trigger whenever the user says "write a skill", "new skill", "create a plugin", "add a skill to the marketplace", "review this SKILL.md", "review my skill", "improve this trigger description", "why isn't my skill triggering", or mentions a SKILL.md file, a trigger description, a skill description, authoring or reviewing an agent skill, or a skills marketplace in any way. Also trigger before authoring any SKILL.md, when editing a trigger description, or when promoting lessons from a private checklist into public skills. If the task is creating, modifying, reviewing, or structuring agent skills or plugins, trigger. When in doubt, trigger.

   8stars