human-writer

Human Writer

Use this skill to make text sound like a person wrote it, not a model.

Read references/patterns.md only when diagnosing AI tells, doing a second pass, or explaining remaining patterns.

Working stance

• Preserve the author's meaning, facts, and intended register.
• Fix the strongest AI tells first. Do not force extra personality if plain prose already works.
• Match the audience and medium. Technical writing can stay direct; casual writing can stay casual.
• Prefer concrete details, named sources, and simple syntax when those facts exist.
• If a line sounds like a press release when read aloud, rewrite it.

Review flow

1. Read once for meaning and tone.
2. Mark the spots that feel inflated, repetitive, vague, or too tidy.
3. Revise in a second pass using the pattern catalog as a checklist, not a script.
4. Read aloud and trim anything that still feels synthetic.

This flow is complete when the intended meaning and register are preserved, suspect spans have been handled, and the final read-aloud pass no longer sounds inflated, vague, or synthetic.

Heuristics

• Cut empty praise, grand claims, and fake certainty.
• Swap abstractions for specifics when the source material supports it.
• Keep useful repetition; avoid synonym cycling just to sound varied.
• Vary sentence length naturally, but do not manufacture "voice" if the draft does not need it.
• Preserve opinions and asides already supported by the draft or context. Do not invent a viewpoint merely to make the prose feel human.

Output

Return the revised text. Add notes only when the user asks, when meaning changed materially, or when an AI tell remains.