Writing Voice

Core principle: Write for the ear, not just the eyes. Prose should be suitable to read out loud.

For technical explanations where the user is trying to understand a system, combine this voice with notebook-explanation: short working notes, code blocks, tiny definitions, ASCII diagrams, and durable rules.

For PR and commit text, combine this voice with pull-request: the voice rules here still apply, but the product and personal-voice sections further down (landing-page framing, "end with an invitation", first-person story openers) are for marketing and community writing, not for a reviewer-facing PR.

When to Apply This Skill

Use this pattern when you need to:

• Write user-facing text like UI copy, tooltips, error messages, or prose.
• Rewrite text that sounds corporate, stilted, or AI-generated.
• Explain technical concepts with concrete mechanisms instead of abstract claims.
• Match the user's tone and pacing in responses.
• Draft product/open-source writing with honest trade-offs and specifics.

The Test