What problem does it solve? Technical documentation often becomes stale, inconsistent, or bloated because teams lack shared standards for writing, formatting, and maintaining it. This Skill encodes Google's documentation philosophy, best practices, and Markdown style guide so agents can write and review docs that stay accurate and readable. ## Core Features & Use Cases - Documentation best practices: Enforces minimum viable documentation, updating docs in the same change as code, deleting dead docs, and structuring the documentation story from inline comments through READMEs and design docs. - Markdown style rules: Applies concrete formatting standards including 80-character line limits, single H1 headings, fenced code blocks with declared languages, informative link titles, reference link placement, and table usage guidance. - README guidance: Defines where README.md files belong and the minimum content every package-level README must include. - Use Case: When drafting a new README for a library or reviewing a documentation pull request, activate this Skill to check structure, heading hierarchy, link style, and freshness against Google's published guidance. ## Quick Start Use the google-documentation-guide skill to review this README.md and suggest improvements based on Google's documentation style guide.
