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 so any tired engineer understands your docs, RFCs, readmes, PR descriptions, and commit messages 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 rules (one instruction per sentence, word limits), and Global English (no ambiguous pronouns, noun strings, or misplaced "only"). - 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 get it rewritten so instructions are commands, conditions come first, real symbol names replace jargon, and every sentence reads one way only. ## Quick Start Ask the AI to review and rewrite your documentation draft using the technical-writing skill's four-layer standard.
