What problem does it solve? Technical docs often fail readers: mixed document types, passive voice, ambiguous sentences, and jargon make them hard to parse on the first read. This Skill gives you a four-layer review standard so docs, RFCs, READMEs, PR descriptions, and commit messages are clear to a tired engineer. ## 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, ~20-word cap), and Global English disambiguation (pronoun clarity, no slashes, no noun strings). - Review checklist: Run an 8-point checklist covering mode purity, instruction structure, word economy, naming consistency, and factual accuracy of symbols and counts. - Use Case: You draft a README for a CLI tool. The Skill rewrites passive configuration prose into direct commands, breaks up a five-noun string, moves the failure condition before the step, and replaces invented metaphors with real symbol names. ## Quick Start Use the technical-writing skill to review and rewrite my README.md following the four-layer standard.
