Make Claude Sound Like You, Not Generic AI
Ask Claude to "write this in a friendly, professional tone" and you'll get exactly that: friendly, professional, and indistinguishable from what anyone else asking for the same thing would get. The problem isn't the output quality. It's that "friendly and professional" describes a category, not a voice, and Claude has no way to know which specific version of that category sounds like you.
Tip
Describing your tone in adjectives gets you the average of every writer who might use those same adjectives. Showing a real sample gets you something closer to actually yours.
You can't describe your way to sounding like yourself. You have to show it.
What actually makes AI writing sound generic
Before fixing it, it helps to know what you're fixing. Generic AI writing tends to share a few specific habits: sentences that run the same length one after another, hedge phrases that soften every claim, and a reflexive "on the one hand, on the other hand" balance even when the situation doesn't call for it. Once you can name these, you'll spot them fast in your own drafts, which is half the battle.
A process for matching your actual voice
- 1
Paste a real sample of your own writing
An email you sent, a Slack message, a paragraph from something you wrote that you'd stand behind. Not a description of your tone, an actual example of it.
- 2
Add a short description alongside it
One or two sentences naming what the sample doesn't make obvious on its own: how formal you are with this audience, whether you use humor, how direct you tend to be.
- 3
Test it on something low-stakes first
An internal message, not a client-facing document. This is where you find out whether the match actually holds before it matters.
- 4
Point at what's off, specifically, if it isn't quite right
"Too formal for this audience" or "that's not how I'd phrase a disagreement" gives Claude something to correct. "Doesn't sound like me" doesn't.
Here's an email I wrote to my team last week: "Hey all, quick heads up that the vendor call moved to Thursday. Nothing needed from you before then, just wanted it on your radar early." Match this tone: direct, casual with this group, no unnecessary preamble. Draft a similar heads-up about Friday's deadline moving to Monday.
”Why one good sample beats a long description
A sample carries information a description can't put into words easily: sentence rhythm, where you put the emphasis, how much you explain versus assume. Trying to describe all of that in adjectives usually just produces more adjectives, which is exactly the generic-sounding trap this article opened with. One real paragraph does more work than three sentences of description.
Consider the difference between "write in a warm, approachable tone" and an actual sample that opens with "Hey, just circling back on this, no rush at all." The description could describe hundreds of different voices equally well. The sample can only describe one, which is exactly why it's more useful: there's nothing left for Claude to guess at.
Inside Claude Tutorial
Matching a real pattern instead of describing one is a transferable skill.
Showing Claude a real example instead of describing what you want in the abstract comes up constantly, well beyond matching your writing voice. The app teaches this pattern through short lessons and hands-on practice.
Compare these two versions of the same paragraph and tell me specifically which one sounds more like typical AI-generated writing, and why: point to sentence length, hedge words, or anything else that gives it away.
”Saving the version that works
Once you've dialed in a sample and description that consistently produce something that sounds like you, that combination belongs somewhere more durable than one conversation. A reusable context brief is exactly the right place to keep it, so you stop re-pasting the same sample every time you start a new chat.
An edge case worth naming
Voice matching works best for your own writing, replying to an email, drafting a message, writing something with your name on it. It matters less for content meant to represent an organization rather than you personally, where a house style guide is the more appropriate source to match, not your personal voice sample.
It's also worth revisiting the sample occasionally rather than treating it as permanent. The way you write shifts depending on the audience, a message to a close teammate reads differently than one to a new client, and a single sample captured months ago may no longer reflect how you'd actually phrase something today. Pasting a fresher sample when the context changes matters more than perfecting the original one.
Continue reading
- Building a Reusable Context Brief You Stop Retyping: where a working voice sample belongs once you've found one that fits.
- Drafting an Email Reply That Actually Sounds Like You: this same idea applied to one specific, everyday task: replying to an email.