Use when creating a new instruction file for a domain, language, or workflow in a customization repo. USE FOR: create a new instructions file, choose applyTo glob for an instruction, write guardrails for a coding workflow, add repository standards for a language, draft instruction frontmatter and naming. DO NOT USE…
Use when creating a new reusable skill with clear triggers, workflow steps, and starter assets in a customization repository. USE FOR: add a new SKILL.md file, design skill trigger phrases, decide if work belongs in a skill, scaffold skill folder with templates, write discovery-focused skill frontmatter. DO NOT USE…
Language-agnostic modernization guidance for incrementally replacing legacy applications using strangler fig, ACLs, and risk scoring. USE FOR: plan legacy app modernization strategy, choose rewrite versus refactor versus replace, design strangler fig migration, sequence service extraction by dependency risk, decide…
Use when reviewing schemas, migrations, indexes, query plans, or data contract safety. USE FOR: audit schema drift, migration rollback safety, index health, query risk, repository patterns. DO NOT USE FOR: UI copywriting, infrastructure-only tasks, generic code review.
Use when designing schemas, writing migrations, reviewing queries, or defining repository and indexing patterns for an application's data layer. USE FOR: design a relational schema, write migration with rollback support, review SQL for N+1 or missing indexes, build a data dictionary, define repository or data access…
Zero-downtime database migration patterns, blue-green cutovers, and rollback strategy guidance for production data changes. USE FOR: plan expand-contract schema migration, design blue-green database cutover, write Flyway versioned migration and undo scripts, prepare rollback plan for production schema change, validate…
Use when capturing ceremony outcomes into durable decision records. USE FOR: document decision, rationale, options considered, owner, and follow-up actions from standup, sprint, and release ceremonies. DO NOT USE FOR: writing implementation code, replacing full ADR workflows, or generating marketing content.
Use when an approved feature or fix should progress to production through governed automation with minimal human intervention. USE FOR: approve-once delivery orchestration, deterministic dry-run rehearsal of status/merge/escalation logic, and policy-aligned remediation payload generation for blocked stages. DO NOT USE…
Use when monitoring workcell BOM dependencies and cell health so blocker issues are opened when a cell fails and resolved when it recovers. USE FOR: dependency maps, cell health checks, blocker issue creation, and recovery closures. DO NOT USE FOR: general project tracking or unrelated CI triage.
VS Code Dev Containers and GitHub Codespaces guidance for reproducible development environments and team onboarding. USE FOR: create devcontainer.json for this repo, set up Codespaces for contributors, containerize local dev toolchain, add VS Code extensions inside container, make development setup reproducible across…
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…
Runs a pull request-scoped triage loop for inbound automated Copilot review threads. USE FOR: impact-sizing review threads, validating Medium suggestions, recording safe dispositions, resolving Small and Medium threads, and escalating Large findings. DO NOT USE FOR: initial pull request review, auto-applying security…
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…
MCP server "basecoat-metrics" as configured in ivegamsft/basecoat. Runs ${workspaceFolder}/mcp/basecoat-metrics/dist/index.js with node. Needs 1 environment variable to run.
★not rated 4 7d agoA
tokens not measured
originalMIT
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…
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: