What problem does it solve? Technical writing from AI agents and developers is often verbose, hard to scan, and inconsistent in tone. This Skill provides an editorial baseline adapted from the Google developer documentation style guide so technical prose, documentation, and agent messages are clear, scannable, and human. ## Core Features & Use Cases - Editorial rule set: Enforces outcome-first structure, active voice, short sentences, parallel lists, and sentence-case headings for technical content. - Agent message adaptation: Provides specific formats for progress updates, error reports, final reports, explanations, choices, and clarification questions. - Source mapping reference: Includes a rule-by-rule mapping to the official Google style guide with documented adaptation decisions. - Use Case: After drafting a long technical report or README, ask the agent to run a readability pass; it restructures the text to lead with the outcome, splits walls of text, and removes filler while preserving exact code and technical terms. ## Quick Start Ask the agent to apply Google developer style to revise the attached technical document for clarity and scannability.
