What problem does it solve? Technical writing often sounds robotic, marketing-heavy, or AI-generated, and READMEs frequently duplicate information already visible in the codebase. This Skill provides concrete style rules, structural patterns, and punctuation guidelines so documentation reads naturally and explains design reasoning instead of restating the obvious. ## Core Features & Use Cases - Technical Article Structure: Enforces a proven deep-dive format with TL;DR, problem-first openings, named concepts, ❌/✅ comparison blocks, trade-off tables, and a closing golden rule. - Voice and Tone Control: Distinguishes instructional versus narrative voice, prioritizes user-provided voice samples, and eliminates AI artifacts like excessive bolding, bullet spam, and marketing adjectives. - README and Punctuation Rules: Guides READMEs to explain the "why" behind organization rather than listing files, and replaces the space-hyphen-space AI artifact with semicolons, colons, or em dashes. - Use Case: When drafting a release announcement or architecture article, apply these rules to produce prose with specific numbers, personal voice, and natural flow instead of structured marketing sections. ## Quick Start Use the documentation skill to review and rewrite my README draft so it explains design decisions in natural prose without AI-sounding language.
