projectb-google-dev-docs-style

Identify the document type first, then apply the style rules: second person, active voice, sentence-case headings, and descriptive link text. This Skill walks through a workflow that consults reference files for voice, formatting, procedures, and links before returning revised content.

The Skill handles concept docs, task and how-to guides, tutorials, reference pages, and troubleshooting content. It also supports READMEs, API docs, and release notes, applying type-specific conventions such as bare-infinitive task headings.

Active voice is the default so the actor stays clear, but passive voice is acceptable when emphasizing the object, de-emphasizing the actor, or when the actor is irrelevant, such as "The database was purged in January."

Use descriptive link text that makes sense out of context, never "click here" or raw URLs. Introduce cross-references with "For more information, see..." and explain unexpected behavior like downloads or new tabs.

Avoid directional language like "above" or "below"; use "preceding" and "following" instead. Provide alt text on images, never skip heading levels, keep sentences under roughly 26 words, and refer to UI elements by their visible labels.

The rules are guidelines, not laws. Project-specific style overrides take priority, and a rule may be broken when doing so improves clarity for the audience, as long as usage stays consistent within the document.