Getting started

Make Claude Write in Your Voice, Not a Robot's

5 minute readUpdated June 2026Explore more

TL;DR

Claude sounds like a robot because you never told it how you write. Three fixes give it your voice: save an output style to lock tone and format, feed it a voice file of your real phrasing and rules, and show it three things you wrote and loved - because examples teach voice faster than adjectives ever will.

Why the default sounds generic

With no instruction, Claude writes to the safe average of everything it has read - hedged, tidy, and faceless. That is not a limit of the model; it is missing input. Voice is learnable, but only if you show it what yours is. Adjectives like 'make it punchy' barely move it. Examples and explicit rules move it a lot.

Fix 1: save an output style

An output style is a saved instruction for tone and format that applies every time, so you stop re-typing 'short sentences, no fluff, no em dashes' in every prompt. Set it once and every answer starts from your defaults instead of the generic ones.

Fix 2: give it a voice file

Write a short file that describes how you actually write - the words you use, the ones you ban, sentence length, how formal, how you open and close. Point Claude at it so your voice is a reference it reads, not something it has to guess each time.

text# my-voice.md
- Short, direct sentences. Lead with the point.
- Plain words over jargon. No buzzwords.
- Never use em dashes; use " - " instead.
- Warm, not stiff. Talk to one person, not an audience.
- Words I use: [list]. Words I never use: [list].

Fix 3: show it three examples

This is the strongest lever. Paste three short pieces you wrote and genuinely liked, and tell Claude to match their voice - not copy the content, match the rhythm, word choice, and structure. Examples carry a thousand implicit rules that no description captures.

Stack all three

  1. 1Output style for the always-on defaults (tone, format, bans).
  2. 2Voice file for the explicit rules and vocabulary.
  3. 3Three examples for everything the rules cannot name.
  4. 4Then review the first few outputs and add any rule you find yourself re-fixing.

Common questions

  • What is an output style?

    A saved set of tone and format instructions that applies to every response, so you do not have to restate your preferences each time. Set your defaults once - length, tone, formatting, things to avoid - and every answer starts from them.

  • Why do examples work better than describing my voice?

    Because your voice is made of hundreds of small choices no description captures - rhythm, word picks, how you open. Three real samples carry all of that at once. 'Make it punchy' is an adjective; a punchy paragraph you wrote is the actual target.

  • How many examples should I give?

    Three short, strong ones is the sweet spot - enough to show the pattern, few enough to stay consistent. Pick pieces you genuinely liked, since Claude will match whatever you feed it, flaws included.

  • Can I have more than one voice?

    Yes. Keep a separate voice file or output style per context - one for posts, one for client email, one for docs - and point Claude at the right one for the job. Same method, different reference.

Want the voice-setup guide with the template?

Get 650+ plug-and-play skills, MCPs & prompts, plus 5,000+ builders - $9/mo, cancel anytime.

Join the Club