What problem does it solve? Writing consistent, well-placed developer documentation is slow and error-prone: pages end up in the wrong location, lack structure, or skip review steps. This Skill enforces a disciplined nine-step workflow that produces focused Markdown documentation with confirmed placement, reviewed structure, and consistent formatting. ## Core Features & Use Cases - Placement rules: Routes component docs to <component>/docs/ and guides or architecture topics to docs/, with a confirmation step before creating files. - Staged authoring workflow: Clarifies scope, gathers source material, proposes location, drafts heading-only structure for approval, then writes content and wires the page into the docs tree. - Writing guidelines: Enforces one sentence per line, Mermaid diagrams, LaTeX math, code blocks, and a standard component template covering purpose, inputs/outputs, algorithm, data structures, and integration points. - Use Case: After adding a new tiling algorithm module, ask the assistant to document it; the Skill reads the source, proposes snp/<component>/docs/index.md, drafts headings for your review, then writes the full page with a Mermaid data-flow diagram. ## Quick Start Ask the assistant to write documentation for a specific component or feature and follow its step-by-step prompts to confirm scope, location, and structure.
