documentation

Remove signs of AI-generated writing from text and revise drafts so they sound natural, specific, and human-written. Use when editing, reviewing, or rewriting documentation, guides, landing pages, release notes, or other prose to reduce AI tells such as inflated symbolism, promotional language, superficial -ing analysis, vague attributions, em dash overuse, rule-of-three cadence, AI-coded vocabulary, passive voice, negative parallelisms, filler phrases, generic conclusions, and chatbot-like framing.

Project-wide specification and test-driven workflow for every development change in this documentation repository. Use before any feature, fix, refactor, content or UI modification, configuration change, or other implementation work, then resume after implementation to verify the agreed acceptance specs. Align on the user's what and why, formalize minimal MMECE outcomes with planned tests, and validate visual documentation at 16:9, 3:4, and mobile sizes.