What problem does it solve? Technical docs, RFCs, READMEs, PR descriptions, and commit messages often read as ambiguous, jargon-heavy, or machine-written. This Skill applies four layered writing standards so a tired engineer understands the text on the first read. ## Core Features & Use Cases - Diátaxis mode selection: Classifies each document as tutorial, how-to, reference, or explanation and enforces the rules of that mode without mixing them. - Sentence-level standards: Applies Google developer style (second person, active voice, condition-before-instruction), STE rules (one thought per sentence, consistent verbs), and Global English (no ambiguous pronouns, slashes, or double readings). - Use Case: You draft a README section explaining a CI budget check. The Skill rewrites vague prose like "configuration is performed via budget.json" into concrete statements with real symbol names, one instruction per sentence, and no words that do no work. ## Quick Start Ask the AI to review and rewrite the attached documentation draft using the technical-writing standard.
