What problem does it solve? Technical docs often confuse readers with mixed document types, passive voice, ambiguous sentences, and jargon. This Skill gives you a four-layer standard for writing and reviewing docs, RFCs, READMEs, PR descriptions, and commit messages so a tired engineer understands them 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 (active voice, commands, condition-first), STE limits (one instruction per sentence), and Global English disambiguation (pronoun clarity, no noun strings). - Review checklist: Run an 8-point checklist covering mode purity, command phrasing, word economy, naming consistency, and factual accuracy of symbols and counts. - Use Case: Paste a draft README section and ask for a review; the Skill rewrites passive constructions, breaks up ambiguous sentences, replaces jargon with real symbol names, and flags mixed Diátaxis modes. ## Quick Start Review this README draft using the technical-writing standard and rewrite any sentences that violate the four layers.
