What problem does it solve? Technical docs often fail readers because they mix document types, bury instructions in passive voice, and leave sentences open to multiple readings. This Skill gives you a four-layer standard so any tired engineer understands your docs on the first read. ## Core Features & Use Cases - Diátaxis mode selection: Classify each document as tutorial, how-to, reference, or explanation, and keep modes from mixing. - Sentence-level rules: Apply Google developer style, Simplified Technical English, and Global English guidelines to instructions, warnings, and pronoun references. - Review checklist: Run an 8-point checklist over docs, RFCs, READMEs, PR descriptions, and commit messages before merging. - Use Case: You are rewriting a confusing README section. The Skill rewrites passive constructions into commands, breaks up noun strings, moves conditions before steps, and replaces jargon with real symbol names. ## Quick Start Ask the assistant to review and rewrite the attached documentation file using the technical-writing standard.
