google-devdocs-style

Produce documentation a developer can act on without rereading: the reader knows who does what, in what order, and what happens next. This skill applies the Google Developer Documentation Style Guide (developers.google.com/style). It is prescriptive by design. Recommend one path rather than listing every option.

Precedence

When sources conflict, follow this order:

1. The user's explicit request and the destination's requirements.
2. Source facts: quotations, code, commands, filenames, API names, UI labels, product names, and version numbers stay exact even when a style rule would prefer something else.
3. Project style. In this repo, AGENTS.md wins. It bans em dash (U+2014) and en dash (U+2013) characters, so use a colon, comma, semicolon, parenthesis, or sentence break, even though Google permits the em dash.
4. The rules in this file.
5. references/ and then the live guide.

Depart from a rule when doing so serves the actual reader. Stay consistent afterward.

Fidelity comes first

Read this before the style rules, because it constrains all of them. A style fix that changes what the document claims is a worse outcome than the defect it removed.