provision-github-tokens

Accessibility and inclusion rules from the Google developer documentation style guide. Covers accessible documentation, inclusive language, and writing for a global audience.

API reference documentation rules from the Google developer documentation style guide. Covers code comments, class/method documentation, parameter descriptions, and API reference formatting.

Formatting rules from the Google developer documentation style guide. Covers text formatting, code in text, code samples, UI elements, HTML formatting, filenames, placeholders, and command-line syntax.

Grammar rules from the Google developer documentation style guide. Covers articles (a/an/the), pronouns, present tense, contractions, and sentence structure.

Image and media rules from the Google developer documentation style guide. Covers alt text, image quality, screenshots, diagrams, and figure formatting.

Naming and terminology rules from the Google developer documentation style guide. Covers capitalization, abbreviations, spelling, and jargon.

Number and date formatting rules from the Google developer documentation style guide. Covers numbers, dates, times, phone numbers, and units of measurement.

Punctuation rules from the Google developer documentation style guide. Covers commas, colons, semicolons, dashes, hyphens, periods, ellipses, slashes, apostrophes, and quotation marks.

Index of skills derived from the Google developer documentation style guide. Provides machine-optimized reference rules for writing and reviewing technical documentation targeting software developers.

Document structure rules from the Google developer documentation style guide. Covers headings, lists, tables, procedures, notices, cross-references, examples, and prescriptive documentation.

Voice and tone rules from the Google developer documentation style guide. Covers conversational tone, active voice, second person, politeness, and restrictions on pre-announcing features.

Word list from the Google developer documentation style guide. Contains recommended and non-recommended terms with alternatives. The full word list is in word-list.json alongside this file.

Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, guides, reference, and explainers.

Create and maintain Architecture Decision Records (ADRs). Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting.