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 writers and reviewers a single layered standard so docs, RFCs, readmes, PR descriptions, and commit messages are understood on the first read. ## Core Features & Use Cases - Four-layer writing standard: Pick the right Diátaxis mode (tutorial, how-to, reference, explanation), write reader-focused sentences per Google developer style, load one idea per sentence per STE rules, and eliminate ambiguity per Global English guidelines. - Review checklist: An 8-point checklist covering mode purity, command-style instructions, sentence splitting, word economy, pronoun clarity, consistent naming, plain vocabulary, and factual accuracy of symbols and counts. - Use Case: When reviewing a README that says "Configuration of the ratchet budget parameters is performed via budget.json", apply the skill to rewrite it as "budget.mjs reads the committed budget from budget.json", fixing passive voice, jargon, and noun strings in one pass. ## Quick Start Use $technical-writing to review and rewrite this documentation file so it follows the layered technical-writing standard.
