What problem does it solve? Documentation often mixes tutorials, how-tos, references, and explanations into one confusing page, or drifts out of sync with the code it describes. This Skill enforces the Diátaxis four-mode separation and provides concrete rules for keeping docs accurate, terse, and maintainable. ## Core Features & Use Cases - Four-mode separation: Keeps tutorials, how-tos, references, and explanations distinct so each doc serves one reader need. - Altitude rules: Docs map the code's wiring and rationale instead of duplicating signatures, flags, and constants that the source already owns. - Design doc skeleton: Provides a reusable template (problem, requirements, invariants, non-goals) for concepts shared across tasks. - Cut patterns: Identifies and fixes common doc smells like migration narration, task IDs in prose, and self-defending paragraphs. - Use Case: When restructuring a project's docs folder, apply this Skill to split a bloated guide into a tutorial, a how-to, and a reference page, then prune stale claims that no longer match the code. ## Quick Start Rewrite the attached onboarding guide as a Diátaxis tutorial, moving theory into a linked explanation doc and cutting any stale claims.
