What problem does it solve? Maintaining consistent, accurate technical documentation across a large repository is difficult. This Skill enforces the Gemini CLI documentation style guide when writing, editing, or auditing Markdown files, ensuring tone, formatting, links, and terminology stay consistent with the codebase. ## Core Features & Use Cases - Style enforcement: Applies rules for voice, grammar, formatting, links, and structure (BLUF, headings, callouts, 80-character wrap) to every documentation change. - Documentation auditing: Runs a multi-phase audit workflow (editor, software engineer, technical writer) that checks the docset against the style guide and verifies code accuracy in packages/. - Terminology guidance: Distinguishes "quota" vs. "limit" usage and other project-specific terminology via the included style guide. - Use Case: When asked to update a page in /docs, the Skill investigates the relevant source code, edits the Markdown per the style rules, checks deep links to changed headings, and finishes with npm run format. ## Quick Start Ask the agent to review and update the getting-started guide in the docs directory so it follows the project documentation standards.
