Use when designing CI/CD pipelines, infrastructure as code, deployment workflows, rollback plans, or observability setup. USE FOR: create GitHub Actions pipeline, review Bicep or Terraform deployment templates, define release promotion gates, write rollback runbook for a service, add monitoring and health checks for…
Use for evidence-based revalidation of older issues and pull requests. USE FOR: classify old issues as still needed, superseded, resolved, duplicate, or recurring; revalidate stale PRs against current code; run oldest-first or scheduled report-only reviews. DO NOT USE FOR: closing items because they are old, sprint…
Use when a contributor asks /basecoat help or needs discovery of intents, agents, skills, or workflows. USE FOR: /basecoat help, help intent, help agents, help skills, help workflows, sample prompts, onboarding vocabulary. DO NOT USE FOR: implementing features, triaging a red CI job, writing new agents.
Triage inbound automated Copilot pull request review threads by the impact of accepting each suggestion. USE FOR: sizing Copilot review threads, validating bounded review suggestions, recording accepted or declined decisions, resolving safe threads, and escalating must-fix findings. DO NOT USE FOR: initial code…
Scaffold a MkDocs Material documentation site with GitHub Pages deployment, navigation, and starter content for a repository. USE FOR: create a docs site for this repo, set up MkDocs Material, publish documentation to GitHub Pages, generate getting-started docs with diagrams, add docs CI workflow. DO NOT USE FOR…
Use when writing or improving technical documentation such as READMEs, ADRs, runbooks, and reference guides. USE FOR: write a project README, record an architecture decision, create an operational runbook, review docs for accuracy and gaps, establish docs-as-code standards. DO NOT USE FOR: implementing application…
Domain-driven design guidance covering bounded contexts, aggregates, event sourcing, CQRS, and saga coordination in complex domains. USE FOR: model bounded contexts and aggregates, design domain events and invariants, apply DDD to microservice boundaries, implement saga orchestration for business workflows, combine…
Structured guidance for assessing and executing modernization from .NET Framework or older .NET targets to modern .NET. USE FOR: inventory a legacy .NET solution, plan phased .NET upgrade, review NuGet and framework compatibility, define modernization test and release gates, remediate breaking changes during…
Use when designing or hardening production E2E tests with Playwright or Cypress, including flake reduction, CI strategy, and browser coverage. USE FOR: choose between Playwright and Cypress, reduce flaky browser tests, test login or checkout journeys, set up cross-browser CI coverage, plan E2E fixtures and mocks. DO…
Use when building secure, production-ready Electron desktop apps with guidance for IPC, preload APIs, packaging, updates, and renderer isolation. USE FOR: secure Electron IPC design, preload script API patterns, package and sign desktop app, implement auto-update flow, review BrowserWindow security settings. DO NOT…
Use when modernizing legacy Entity Framework data layers to EF Core with help for model mapping, DbContext refactors, phased cutovers, and migration risk review. USE FOR: migrate EF6 to EF Core, refactor DbContext configuration, convert model mappings and conventions, plan phased database cutover, validate query…
Audit environment-map.yml against expected Azure and GitHub state to detect configuration, security, deployment, and tagging drift before automation runs. USE FOR: scheduled drift audits in CI, pre-deployment drift gates, identifying branch-protection mismatches to autonomy levels, and producing remediation-first…
Use when bootstrapping secure Azure delivery environments with OIDC federation, state storage, Key Vault, promotion workflows, and Fabric access automation. USE FOR: set up GitHub Actions OIDC to Azure, provision Terraform state storage, configure Key Vault for CI/CD secrets, design dev-to-prod environment promotion…
Use when routing high-risk decisions to the right human approver with a PR-comment approval trail. USE FOR: release signoff, irreversible changes, compliance gates. DO NOT USE FOR: routine automation.
Use when defining factory state transitions, reading or writing .github/factory-state.json, or orchestrating workcell workflow gates. USE FOR: intake/complete/pending transitions, auto-proceed rules, escalation checks, and state validation. DO NOT USE FOR: general app state management or unrelated workflow docs.
Use when running the failure-pattern consumer process from mining through enhancement planning. USE FOR: evidence mining, append-only raw finding capture, common-versus-local triage with rationale, and prioritized enhancement planning with early-detection gates. DO NOT USE FOR: implementing repository feature changes…
★not rated 4 todayA71 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: