Create simple, beautiful visual explainers for people new to a topic. Use for ELI5 and picture-first requests.
Review a pull request or queue from problem value through code correctness. Use for new review, rereview, batch review, or deciding findings and next steps. Do not use to implement feedback, report status, draft, merge, or monitor checks.
Use this skill whenever existing code-review feedback may lead to a code decision or edit, including PR comments and findings from external models, review tools, or delegated reviewers—even when the user simply says to fix, address, apply, or resolve them. Do…
Audit an existing repository or scoped architecture area for simplification opportunities, separating proven removals from those still blocked on a fact or a decision. Use when asked to find what can be removed or consolidated, reduce codebase-wide…
Teach with adaptive guidance, retrieval practice, and Socratic questioning. Use when the user wants to study a topic, build durable understanding, practice, or be coached. Do not use for one-off factual answers, quick explanations, or ordinary task guidance.
Test-driven development for production behavior. Use whenever implementing a feature, fixing a bug, or changing observable production behavior that can be exercised by a fast, reliable automated test through a stable public seam. Also use before refactoring…
Draft or review minimal, testable goals. Use only when the user explicitly asks to write, revise, or review a goal.
Test-driven development for production behavior. Use whenever implementing a feature, fixing a bug, or otherwise changing observable production behavior, and before refactoring to establish or verify a green safety net. Do not use for docs-only changes,…