documentation
Documentation
Route documentation tasks to the right reference and execution path.
Routing
Determine the task type from arguments and context, then load the matching reference:
| Signal | Task type | Load | Execute with |
|---|---|---|---|
Source file path (.ts, .js, .py, .go, .rs, etc.) |
Code comments | references/code-comments.md | @ce:haiku agent |
| Mentions "comments", "inline docs", "code comments" | Code comments | references/code-comments.md | @ce:haiku agent |
| "Clean up comments" in a folder or unstaged changes | Code comments | references/code-comments.md | @ce:haiku agent |
Markdown file path (.md) |
System docs | references/systems.md | General subagent |
Mentions README, API docs, architecture, /docs/ |
System docs | references/systems.md | General subagent |
| Multi-file scope or new documentation | System docs | references/systems.md | General subagent |
| Ambiguous | - | Ask user to clarify scope | - |
Execution
More from rileyhilliard/claude-essentials
design
Enforces precise, minimal design for dashboards and admin interfaces. Use when building SaaS UIs, data-heavy interfaces, or any product needing Jony Ive-level craft.
18writer
Writing style and tone guide for human-sounding content. Use when writing documentation, READMEs, commit messages, PR descriptions, blog posts, or any user-facing content.
17strategy-writer
Produces executive-quality strategic documents in The Economist/HBR style. Use when writing strategy memos, market analysis, business cases, customer research reports, or any document for Product, Design, and Business leaders. Customer-led, evidence-based, narrative-driven.
13systematic-debugging
Debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.
13executing-plans
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
12refactoring-code
Improves code structure while preserving behavior through test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.
12