What problem does it solve? Inconsistent tone, grammar, and terminology across code comments, READMEs, API docs, and PR descriptions make a repository harder to read and maintain. This Skill gives the AI a concrete, working subset of the Google developer documentation style guide so every piece of prose it writes or edits follows the same rules. ## Core Features & Use Cases - Style rules for prose: Enforces active voice, present tense, second person, sentence-case headings, serial commas, and condition-before-instruction phrasing. - Artifact-specific guidance: Adapts person and shape for Markdown docs, HTML help text, godoc/rustdoc/JSDoc/Swift API comments, inline comments, and PR descriptions. - Word list and examples: Ships reference files with preferred term replacements (for example, allowlist instead of whitelist) and before-and-after rewrites for docs and comments. - Use Case: While drafting a Go doc comment or revising a README section, the AI applies these rules automatically, replacing filler words like "just" and "simply" and rewriting passive constructions. ## Quick Start Ask the AI to review or rewrite a README section, code comment, or PR description using the Google developer documentation style guide.
