technical-writing

Scan the draft against a checklist of AI writing tics: stock vocabulary like "delve" and "seamless", trailing "-ing" benefit phrases, em dashes, and stacked hedges. Rewrite each hit with the concrete fact, number, or mechanism, keeping the original meaning.

State what changed with the actor and mechanism named, such as which file reads which option, and include the proof like a test result or issue number. Cut welcomes, sign-offs, and benefit claims that the text cannot back with a fact.

A tutorial teaches by doing, a how-to completes a known task, a reference lists what exists, and an explanation says why. Each document should pick one mode; a Usage section is a how-to or reference, so it opens on the command rather than a welcome.

Do not use it for chat replies, code comments, or product interface strings, which follow their own style rules. It also does not set the structure of PRs, issues, commits, or briefs; it only words the text inside fields other skills define.

No. Over-compressed telegraphic text forces the reader to decode it. Keep articles and verbs, write whole sentences with one thought each, and split sentences past 25 words; clarity outranks brevity.