USE FOR: Clarify concepts before names harden by fixing concrete referents, roles, sequence, candidate terms, and first-use definitions. Use for terminology-heavy design docs, research synthesis, cause-isolation or mitigation plans, naming decisions, and reasoning-order summaries only when concept/referent ambiguity…
USE FOR: $create-review-comment, ai-create-review-comment, or terse PR-review-comment requests. Infers the PR and routes postman substantive review through guardian/critic without exposing mechanics. DO NOT USE FOR: unrelated tasks, broad rewrites, generated outputs, or posting comments without explicit approval.
USE FOR: Repo-local BigQuery, Databricks, dbt, restricted BigQuery/dbt safety, and cloud auth workflows. DO NOT USE FOR: harness, diagrams, or generic code.
USE FOR: draw.io and Mermaid diagram authoring, preview, export, layout, color, and asset workflows in this repo. DO NOT USE FOR: data-platform or generic coding tasks.
USE FOR: Reference-only provider-pack lookup and promotion decisions for Cloudflare, dbt, Azure, Databricks, AWS, Terraform/HashiCorp, Google Workspace, and Streamlit. DO NOT USE FOR: repo guardrails, harness work, active promotion without explicit request, or Cloudflare security audits.
USE FOR: Programming/debugging: Bash, Python/Jupyter quality, Nix package workflow, Terraform with Checkov, Markdown, TDD/Tidy First, and root-cause isolation. DO NOT USE FOR: agent harness, data-platform, diagramming, or GitHub workflow work.
USE FOR: Guardian/critic native multi-perspective review workflow, peer critic evidence, material-finding convergence, and blocking-finding synthesis. DO NOT USE FOR: implementation, dispatcher fan-out, overrides, or public posting.
USE FOR: Verifying technical claims, comparing options, and investigating unfamiliar libraries/APIs/tools with cited, confidence-rated evidence. DO NOT USE FOR: implementation, opinion without evidence, or tasks better served by a narrower repo-specific skill (e.g. data-platform, dev-platform-workflow).
USE FOR: Implement, fix, add, or otherwise change any code in the current repository — read this BEFORE starting, and before any git or GitHub action (issue, branch, commit, push, PR create/review) — sets the issue-first, worktree-based default via issue-worktree-create. GitHub/Jira/Confluence: gh CLI, PR/commit/issue…
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: