Documentation Skill
Write and review documentation following Labee standards.
Core Principles
- •Clarity over completeness - Write what is necessary, no more
- •Consistent structure - Follow established patterns
- •Actionable content - Every document should help readers accomplish something
When Invoked
Step 1: Identify Task Type
- •Writing new docs? → Go to Step 2a
- •Reviewing existing? → Go to Step 2b
- •Formatting questions? → Load markdown-formatting.md directly
Step 2a: Writing New Documentation
- •Load
references/content-types.mdto choose document type - •Load
references/document-structure.mdfor structure template - •Apply writing principles from
_core-rules.md(auto-loaded) - •Draft document following templates
Step 2b: Reviewing Documentation
- •
_core-rules.mdis auto-loaded with P1 rules - •Check against rules, noting specific issues with line numbers
- •Categorize issues by priority (P1 must fix, P2 should fix, P3 nice to have)
Step 3: Provide Output
For writing: Provide draft following templates For review: List specific issues with:
- •Line number
- •Issue description
- •Suggested fix
Reference Files
| File | Use When |
|---|---|
| references/_core-rules.md | Auto-loaded: Essential P1 rules for all documentation |
| references/writing-principles.md | Voice, tone, grammar, inclusive language |
| references/document-structure.md | Structuring documents |
| references/markdown-formatting.md | Markdown syntax questions |
| references/file-organization.md | Organizing files/folders |
| references/content-types.md | Choosing document types |
| references/code-examples.md | Including code in docs |
| references/ai-documentation.md | Writing AI context files |
| references/project-structure.md | Project documentation |
| references/culture-principles.md | Company values/culture |