| name | documentation-standards |
| description | Clear technical documentation — JSDoc, Mermaid, READMEs, ADRs, C4 diagrams, ISMS policy citations |
| license | MIT |
Documentation Standards Skill
Context
Applies when writing READMEs, documenting APIs/functions/classes, creating architecture docs, adding JSDoc, drawing diagrams, writing ADRs, documenting security policies, or writing user guides.
Aligned with the architecture-documentation expectations in
Secure Development Policy §Architecture Documentation Matrix.
Rules
- ISMS References — security-relevant docs cite the applicable Hack23 policy
- JSDoc for Public APIs — every export gets
@param, @returns, @example (and @throws where relevant)
- Include TypeScript types in JSDoc context (types live in code; JSDoc describes behavior)
- Working examples — every snippet compiles and matches current behavior
- Document exceptions —
@throws for every thrown error type
- Mermaid diagrams — never screenshots; always include source
- Keep READMEs current — updates ship in the same PR as code changes
- Link authoritative external docs — React, Three.js, vitest, ISO/NIST/CIS
- Show anti-patterns —
❌ examples beside ✅ for high-impact APIs