Write Technical Docs

Produce task-oriented documentation that is accurate, easy to scan, accessible, and usable by a global technical audience. Treat the Google guide as editorial guidance rather than a substitute for product facts, project requirements, or user intent.

Establish Authority and Scope

Apply guidance in this order:

1. Follow explicit user instructions and the target project's documented style, terminology, templates, and lint rules.
2. Follow this skill and the Google Developer Documentation Style Guide where project guidance is silent.
3. Preserve intentional local consistency when changing it would create a mixed or misleading document.
4. Ask for a decision only when competing interpretations materially change meaning, audience, or required structure.

For non-English content, apply the workflow, information design, accessibility, code, UI, and linking guidance. Do not impose US English grammar, spelling, capitalization, or punctuation on another language.

Never invent commands, flags, API behavior, prerequisites, outputs, product names, links, or compatibility claims. Mark unresolved facts or ask for evidence instead.

Select References