Outline Driven Development

Use when evaluating whether a bug issue has sufficient detail and identifying missing reporter information. Not for non-bug issues or backlog triage: use github-backlog-triage.

中文简介正在准备中。当前显示原文说明。

Use when a human explicitly asks to ship work through a clean branch and pull request. Don't use for force-pushing, reusing conflicting branches, or widening the change scope.

中文简介正在准备中。当前显示原文说明。

Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts. Not for people-mediation conflicts: use culture-conflict-mediation.

中文简介正在准备中。当前显示原文说明。

Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.

中文简介正在准备中。当前显示原文说明。

Use when a human explicitly invokes a watcher cycle for an open pull request that must be watched until mergeable or blocked. Not for merge, force-push, or work outside the invoked cycle.

中文简介正在准备中。当前显示原文说明。

Use when a human directly requests review and publication of an existing diff or delegated work. Not for merging pull requests, force pushes, history rewrites, or deployment.

中文简介正在准备中。当前显示原文说明。

Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.

中文简介正在准备中。当前显示原文说明。

Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.

中文简介正在准备中。当前显示原文说明。

Use when asking "overkill?", "elegant?", "audit", or "taste-test this", or setting a taste register. Not for tasks that require source or remote-system changes.

中文简介正在准备中。当前显示原文说明。

Use when the user requests an accessibility audit, a11y check, or WCAG compliance review. Don't use for tasks that require source or remote-system changes.

中文简介正在准备中。当前显示原文说明。

Use when directing, building, or auditing React/Next.js Tailwind UI: visual direction, responsive/dark-mode retrofits, UX audits. Not for typography or motion: use typography-audit or ui-animation.

中文简介正在准备中。当前显示原文说明。

Use when writing, editing, cleaning, or refactoring Tailwind classes, components, or configuration. Not for read-only audits of Tailwind code, or general CSS without Tailwind.

中文简介正在准备中。当前显示原文说明。

Use when asked to build or modify production-quality components, layouts, state, and pages with WCAG 2.1 AA and real content. Not for token-system design: use frontend-design-deslop.

中文简介正在准备中。当前显示原文说明。

Use when asked to push an already-working artifact to finished composition, texture, and feel. Not for remote or irreversible changes. Not for hygiene routing: use clean-and-true.

中文简介正在准备中。当前显示原文说明。

Use when a visual needs repeatable fixed-view rendering and independent rubric scoring. Not for free-form visual review or subjective critique.

中文简介正在准备中。当前显示原文说明。

Use when starting UI work, defining palettes or tokens, fixing AI-generic UI, or persisting a design system to DESIGN.md (modes: implement, persist). Not for live URLs: use web-design-review.

中文简介正在准备中。当前显示原文说明。

Use when /design-variants generates distinct design directions and a gallery for selection. Not for one polished artifact: use polished-web-prototype. Not for token-system picking: use design.

中文简介正在准备中。当前显示原文说明。

Use when a query needs direct SMT solving, an unsat core needs debugging, or another tool reports a solver timeout or unknown. Not for deciding what to prove: use proof-driven.

中文简介正在准备中。当前显示原文说明。

Use when creative work is requested with no approved design, or a raw idea or repository must be developed into an approved design document. Not for work with an approved design in context.

中文简介正在准备中。当前显示原文说明。

Use when asked to audit typography across a codebase. Produces a file:line report with concrete fixes ordered by impact and flags unverifiable rules. Not for building a type system or token scale.

中文简介正在准备中。当前显示原文说明。

Use when asked to build spring, easing, gesture, and choreographed animations with correct physics and reduced-motion support. Not for auditing existing motion or finding animation opportunities.

中文简介正在准备中。当前显示原文说明。

Use when effectful, security-sensitive code needs refinement-typed, SMT-backed verification in F*, in the HACL* or Project Everest style.

中文简介正在准备中。当前显示原文说明。

Use when asked to design, write, review, refactor, lint, or performance-diagnose Lean 4 proofs, libraries, or tactics. Not for non-Lean code or changes outside source, API, proof, or linter scope.

中文简介正在准备中。当前显示原文说明。

Use when a proof needs Rocq (formerly Coq), including legacy Coq codebase maintenance and migration through the Coq to Rocq rename. Not for Lean 4: use writing-lean-proofs.

中文简介正在准备中。当前显示原文说明。