docs-writer

Read the relevant source code first to confirm actual behavior, then write docs that describe only what the code does. This Skill instructs the agent to investigate the packages directory before writing or editing any documentation file.

Identify gaps where docs no longer reflect the code, fix passive voice and awkward wording, and check terminology consistency. The Skill follows an editing sub-process covering gaps, tone, clarity, and consistency before verifying links.

The style guide in references/style-guide.md requires active voice, second person, present tense, sentence-case headings, serial commas, 80-character text wrapping, and descriptive link text. It also covers accessibility and filename conventions.

Do not use it for code comments, inline JSDoc, or API reference generation, as stated in its description. It is scoped to prose documentation such as READMEs, guides, and docs directory pages.

Yes. When adding a new page it checks whether docs/sidebar.json needs updating, and during finalization it verifies the validity of all links in new content and links pointing to changed or deleted pages.