What problem does it solve? Maintaining consistent, accurate technical documentation across a large project is difficult. This Skill enforces the Gemini CLI documentation style guide when writing, editing, reviewing, or auditing Markdown files in the /docs directory, ensuring content matches the current codebase. ## Core Features & Use Cases - Style Enforcement: Applies voice, tone, grammar, formatting, link, and structure rules (80-character wrap, sentence case, BLUF, callouts) to every documentation change. - Documentation Auditing: Runs a three-phase audit workflow (Editor, Software Engineer, Technical Writer) that finds style violations, verifies code accuracy against packages/, and identifies undocumented features. - Terminology Consistency: Uses the quota vs. limit style guide to keep resource-capacity wording consistent across user-facing content. - Use Case: When asked to document a new CLI command, the Skill investigates the implementation in packages/, writes the page following all standards, checks cross-references and docs/sidebar.json, and finishes with npm run format. ## Quick Start Use the docs-writer skill to write a new documentation page for the recently added CLI command and verify it against the style guide.
