con un clic
sdd-skills
sdd-skills contiene 10 skills recopiladas de zhijunio, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
Use when creating or revising AGENTS.md for a repository—agent operating context, commands, and conventions. Not README.md, CONTRIBUTING, or full API documentation unless the user asks.
Use when creating or revising README.md for a project—comprehensive human onboarding for developers. Not AGENTS.md, CONTRIBUTING, or full API documentation unless the user asks.
Whole-repo (or named-scope) audit for over-engineering only: ranked cuts to delete, simplify, or replace with stdlib/native. Use for "audit for over-engineering", "what can I delete", "find bloat", "ponytail-audit". One-shot report; does not apply fixes. Not a full Standards health scan or increment quality report.
Use when an approved plan is ready for test-first implementation, or when review findings must be fixed without changing accepted behavior. Not spec/plan revision unless blocked.
Broad-scope Standards scan for improvement candidates. Use when the user wants a repo, module, area, or branch health/improve pass — hotspot-first, four-dimension report, pick a candidate next. Not increment delivery review.
Use when an approved specification needs decomposition into testable vertical slices before implementation. Not clarifying product behavior or writing code unless the user asks.
Two-axis Standards/Spec review of changes since a fixed point. Use when the user wants a branch, PR, or "review since X" quality report. Not whole-repo improve scan.
Use when a software change needs a durable behavior contract, scope, acceptance criteria, and technical constraints before implementation planning. Not implementation, open-ended design interviews, trivial one-line fixes, or fully specified direct edits.
Use when the user wants a clear explanation of selected code or a snippet—overview, walkthrough, concepts, and examples. Not implementation, refactoring, or test generation unless the user asks.
Use when a new contributor needs a phased onboarding plan for this repository—environment setup, codebase exploration, and first tasks. Not implementation, spec, or delivery review unless the user asks.