Style Guide
Style Guide
Write the way you would explain the work to an engineer from another company: plain, direct and in your own voice.
- Open with the concrete problem or event, not with background about the industry.
- Explain every internal name (products, teams, tools, metrics) the first time it appears.
- Say what a book, framework or scale argues when you cite it. Naming it is not enough.
- Cut padding: qualifiers, throat-clearing, and sentences that restate the previous one.
- Never use em dashes. Use commas, colons or parentheses instead.
/blog-review checks a draft against these points. See Writing with Claude Code.
Even more about style!
If you are curious and want to know how professional publishers go about keeping their articles consistent in word an grammar, we recommend these resources: