human-voice-writinglisted

# Human Voice Technical Writing ## Overview A systematic writing methodology that eliminates synthetic "AI-isms" (filler phrases, robotic customer-service tone, repetitive conclusions) and produces technical content with authentic human voice, grounded engineering insights, and engaging rhythm. ## When to Use & When NOT to Use ### When to Use - Writing tech blog posts, tutorials, and architecture case studies. - Refining AI-generated drafts into natural, engaging prose. - Creating developer-focused changelogs, README showcases, and social posts. ### When NOT to Use - Strict API documentation or JSON schema specs requiring purely mechanical descriptions. - Formal legal compliance disclosures or raw telemetry logging. ## Core Writing Rules & Negative List | Category | ❌ Strict Negative List (Never Use) | ✅ Human Alternative (Use Instead) | |---|---|---| | **AI Clichés** | "In today's fast-paced digital world...", "Delve into", "Tapestry" | Start directly with the core problem or command | | **Robotic Openings** | "First and foremost...", "Let's embark on a journey..." | "Here is the exact setup that works in production:" | | **Empty Summaries** | "In conclusion...", "It is important to remember that..." | End with a verification command, next step, or sharp tip | | **Fluff Transitions** | "Moreover, it is worth noting that...", "Furthermore..." | Use clean bullet points or jump straight to the point | ## Structure of a Top-Tier Technical Post 1. **🎯 The Hook & Core Go