writing-voice

Original：🇺🇸 English

Translated

Voice and tone rules for all written content. Use when writing prose that should sound human and be suitable for reading aloud.

2installs

Added on2026-02-07

NPX Install

npx skill4agent add epicenterhq/epicenter writing-voice

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

Read it out loud. If it:

Patterns that scream "AI wrote this":

Bold formatting everywhere: Never bold section headers in body content
Bullet list everything: Convert to flowing paragraphs when possible
Marketing words: "game-changing", "revolutionary", "unleash", "empower"
Structured sections: "Key Features:", "Benefits:", "Why This Matters:"
Vague superlatives: "incredibly powerful", "seamlessly integrates"
Dramatic hyperbole: "feels like an eternity", "pain point", "excruciating" — use facts instead
AI adjectives: "perfectly", "effortlessly", "beautifully", "elegantly"
Space-hyphen-space: "The code works - the tests pass"
Overusing fragments: "Every. Single. Time." (once is emphasis, twice is a pattern)
Staccato buildup: Setup. Fragment. Fragment. Fragment. Punchline. This "dramatic reveal" pattern feels manufactured. Combine into one flowing sentence with em dashes or semicolons instead.
Forced specificity: Random numbers that don't add meaning

Never use " - " (space-hyphen-space) or " — " (space-em-dash-space). Prefer simpler punctuation:

Prefer	When
Period (.)	Default choice. Two sentences are often clearer than one.
Colon (:)	Introducing explanation: "Here's the thing: it doesn't work"
Semicolon (;)	Related independent clauses: "The code works; the tests pass"
Em dash (—)	Sparingly, for interruption or emphasis: "It's fast—really fast"

Em dashes are fine but easy to overuse. When in doubt, use a period.

When the user provides example text or tone guidance, match it: