skills.rest
EpicenterHQ
EpicenterHQOFFICIAL
Explore all skills by this author →
Website𝕏@EpicenterHQGitHub

google-devdocs-style

Write and audit developer documentation against the Google Developer Documentation Style Guide.

4.8k|376|Updated Mar 16, 2023
Search Tags:#Technical Writing#Documentation#developer docs#style audit#Google style guide#Editing
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill google-devdocs-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: google-devdocs-style
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill google-devdocs-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developer documentation often suffers from inconsistent voice, ambiguous instructions, and style drift across pages. This Skill applies the Google Developer Documentation Style Guide so guides, API references, READMEs, procedures, and release notes read clearly and consistently.

Core Features & Use Cases

  • Drafting and rewriting: Produces documentation in Google style with active voice, present tense, second person, and condition-before-instruction phrasing.
  • Style audits: Reviews existing documents and reports findings in priority order without rewriting when only an audit was requested.
  • Fidelity preservation: Keeps source facts, modals, qualifications, code tokens, UI labels, and links intact while fixing style.
  • Use Case: Paste a draft README section and ask for a Google-style revision; the Skill rewrites it, flags unsupported claims, and preserves every technical detail.

Quick Start

Ask the assistant to rewrite the attached documentation draft in Google developer documentation style while preserving all technical facts and links.

Frequently Asked Questions about google-devdocs-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write documentation in Google developer documentation style?▼

Provide the draft or topic and ask for a Google-style revision. The Skill applies active voice, present tense, second person, sentence-case headings, and condition-before-instruction phrasing, then runs a fidelity pass to preserve your facts and links.

What documents does the Google style guide apply to?▼

It applies to guides, API reference, READMEs, procedures, and release notes. It does not apply to UI strings, commit messages, PR bodies, code comments, quotations, or legal text.

Can it audit documentation without rewriting it?▼

Yes. When asked for an audit, it reports findings in priority order with bounded examples and returns questions only the product owner can answer, rather than guessing at replacement wording.

Does Google style allow em dashes in documentation?▼

Google style permits em dashes, but this Skill follows the repository's AGENTS.md, which bans em dash and en dash characters. It restructures sentences using colons, commas, or parentheses instead.

What are the limitations of automated style checking?▼

The Skill's references are a synthesis, not a reproduction of the full guide. For disputed words or specialized formats it points to the live guide pages, and it does not claim full compliance without checking them.

Related Skills

Explore More Content & Communication Skills→
friedbotstudiofriedbotstudio
5

prose

Draft and revise English prose from source facts for documentation and summaries.

Official
Advanced
oletizioletizi

editorial-status

Read editorial calendar files and group entries by workflow stage.

Community
Intermediate
outfitter-devoutfitter-dev
6

docs-audit

Audit markdown documentation against the current codebase state.

Official
Advanced
duanbiao2000duanbiao2000
3

doc-framework-annotator

Annotate DocFramework/ documentation with bilingual insights and heuristic questions.

Community
Intermediate