Write Technical Docs

Produce accurate, task-oriented, scannable, accessible documentation. Project facts, user intent, and local style outrank general editorial guidance.

Establish Authority

1. Follow explicit user instructions and project terminology, templates, lint rules, and neighboring docs.
2. Apply this skill and Google guidance where local rules are silent.
3. Preserve intentional consistency unless it misleads readers.
4. Ask only when competing interpretations materially change meaning, audience, or structure.

For non-English content, apply information design and accessibility without imposing US English grammar or punctuation. Never invent commands, flags, API behavior, prerequisites, output, compatibility, names, or links.

Load Only Needed References