Powercademy's living conventions for Power Platform delivery — Dataverse schema judgement (statecode over custom status, solution and publisher discipline, dependency packaging), the Power Automate and PCF lessons that cost hours once (editing live flows, child-flow contracts, whether PCF is the right tool, the premium-licensing trap), applied before and alongside any build, model-driven app UX (every command button has an icon that says what it does, modal focused-task dialogs), the tool-selection ladder (purpose-built tools, then SDK / Web API / CLI, browser automation only where nothing else reaches), plus the writing-skills house standard for authoring skills that work in both runtimes. Each rule carries its reasoning; the lists grow with every corrected mistake.
Plugin conventions from marketplace powercademy-skills in Powercademy/powercademy-skills. Commands read from the repo's manifest — today.
dataverse-conventionsApply 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
flow-conventionsApply 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, bl
model-driven-uxApply 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, pai
pcf-conventionsApply 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 cont
tool-selectionPick 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
writing-skillsThis 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 wil
Power Platform ALM the Powercademy way — design the delivery process (environments, solution segmentation, publisher, the config boundary, promotion path and approvals), then run promotions with checkpoints that stop before anything irreversible. Routes execution to Microsoft's Dataverse solution skills, native pipelines and pac CLI rather than rebuilding them. A production import is always a red checkpoint.
2 skills · 1 MCP server
Make the canvas app decisions that generation can't — is canvas even the right shape, delegation and data strategy, screen and navigation architecture, conventions — then hand a decided build plan to Microsoft's canvas authoring tooling. Checkpoints at real data volumes, because a 50-row test proves nothing. Methodology, not mechanics.
1 skill · 1 MCP server
Takes a machine from nothing to fully equipped for end-to-end Power Platform development, then keeps it healthy. setup-workstation asks which workloads you'll build, installs the SDKs, CLIs, Microsoft's plugins and MCP servers with one approval, and writes an IT request for anything needing admin rights; check-setup diagnoses and repairs auth profiles, tenants, outdated tools and plugin drift. Both read one versioned toolchain manifest that a weekly upstream watch keeps current.
2 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
200 skills · 98 commands · 71 agents · 1 MCP server · hooks
AgentDB memory controllers with HNSW vector search, RuVector embeddings, and causal graphs
2 skills · 2 commands · 1 agent
Editorial diagrams in your brand, as self-contained HTML and SVG. Architecture, flowcharts, sequence, state machines, ER and database schemas, timelines, swimlanes, org charts, Gantt, Wardley maps, user journeys, service blueprints, UML class, lifecycle phase maps, and charts from bar, line and scatter to Sankey, treemap and heatmap, plus many more. Redraws draw.io, Mermaid, Excalidraw and PlantUML files. Exports SVG and PNG.
1 skill · 7 commands
Connect Claude Code directly to your CockroachDB clusters for hands-on database work — explore schemas, write optimized SQL, debug queries, and manage distributed database clusters. This plugin provides 14 tools across two active MCP backends (self-hosted MCP Toolbox and managed CockroachDB Cloud MCP Server), three specialized agents (DBA, Developer, Operator), 32 skills across 6 operational domains, and built-in safety hooks.
34 skills · 3 agents · 3 MCP servers · hooks
Database architecture, schema design, and SQL optimization for production systems
1 skill · 2 agents
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.