How to Get Claude to Write in Your Voice

Most AI writing is immediately obvious. Triadic adjectives ("clear, concise, and compelling") and setup/payoff openers ("Here's the thing:") are both tells that a language model wrote your memo. If you've ever asked Claude to draft something and then spent 20 minutes editing out everything that sounds off, you'll be familiar with this problem. The driving factor behind it is that Claude has no evidence of how you actually write.

The solve: build a voice guide once (a document that captures your actual vocabulary, sentence structure, and writing patterns) and have Claude reference it every time you need to write. Claude will learn how to sound like you, and the time you spend editing outputs will drop significantly.

This guide shows you how to build a voice guide, refine it so it feels accurate, and tell Claude when to use it.

Step 1: Gather Examples of Your Writing

Claude needs evidence to understand your voice. The more examples you give it, the more accurate the guide will be.

Aim for 8-10 samples of your writing across different contexts. Don't just pull your most formal work. Pull in writing that represents how you actually communicate day-to-day.

Good sources to pull from:

Professional emails you sent and felt good about
Proposals, memos, or longer internal documents
LinkedIn posts, newsletters, or any public writing
Anything you wrote relatively quickly and didn't over-edit (these tend to reveal your natural rhythm most clearly)

Variety is useful here. Your LinkedIn posts and your client emails probably have different levels of formality but the same underlying voice. Giving Claude both shows it the constant underneath the variables. You don't need to paste 30 pages of material: 100-150 words per example is enough for Claude to identify patterns.

💡 Tip

Include at least one piece you're proud of and one you dashed off quickly. The proud piece shows your aspirational voice; the quick one shows how you write when you're not thinking about it.

Step 2: Let Claude Derive Your Voice Guide

Paste all your examples into a single Claude message with this prompt at the end:

Paste this into Claude

"Here are [X] examples of my writing. Analyze them and create a voice guide I can use to instruct Claude to write in my voice. Focus on: the vocabulary I use naturally, my sentence structure and rhythm, how I organize and format information, and the words, phrases, and sentence patterns I should avoid because they'd sound out of character. Save these examples of my writing as 'examples' in the voice guide. Also flag any patterns that read as AI-generated that I should explicitly ban. Save this as a document called [Your Name] Voice Guide."

When Claude produces the guide, ask Claude to save it for you (a Notion page, a Google Doc, or a text file all work). If you've set up a Personal Operating System with a context folder, this is a natural file to add there.

Claude will read across all your examples and produce a guide covering your vocabulary, your structural habits, your voice signatures, and, importantly, what should be avoided. That last section tends to be the most valuable: Claude is good at identifying AI-sounding patterns precisely because it knows what those patterns are.

👉 Example

You paste in 6 longer work emails, 3 internal memos, and 2 LinkedIn posts. Claude produces a guide that identifies your habit of opening every paragraph with a direct claim, your preference for parenthetical asides over em dashes, a vocabulary list of words you naturally use, and a list of patterns you avoid. 10 minutes of work will save editing time on every piece of AI-assisted writing going forward.

Step 3: Review and Refine

Read the voice guide carefully. Claude's analysis is usually accurate on structure and vocabulary (it's good at spotting patterns across a body of writing). Where it tends to miss: anything about why you write the way you do, and how your tone shifts across contexts.

Two questions to ask yourself:

What did it get right that you wouldn't have thought to say? These are often the most valuable entries: patterns so natural to you that you've never had to articulate them.
What did it overstate or get wrong? Edit those entries directly.

Then pressure-test it: ask Claude to write one short paragraph in your voice on a topic you'd actually write about, then read it. If something feels off, trace it back to the guide (you can do this directly in conversation with Claude) and ask Claude to fix the relevant rule. It usually takes 2-3 rounds of testing and refining before the guide produces consistently good results.

Add anything it missed: topics you cover often, audiences where your register shifts, domain-specific vocabulary that's part of your professional identity.

Step 4: Put the Guide to Work

There are two main ways to deploy your voice guide, in order of setup required:

Load it into a Claude "Writing" Project. Projects are persistent workspaces in Claude. Navigate to Projects via the left sidebar of Claude.ai (or go directly to claude.ai/projects), then click "+ New Project" in the upper right corner. Each Project has its own instructions that load automatically for every conversation inside it. Create a Project for your writing work, paste the voice guide into the Project Instructions, and every conversation in that Project will automatically inherit your voice.

Save it in a connected folder. If you use Claude Cowork with a connected folder on your computer (your Context folder would be ideal), drop the guide in and reference it in your global instructions: "Always read [Voice Guide filename] before writing anything in my voice." Cowork will read it automatically. Global instructions are found under Claude → Settings → General.

(Not recommended) Paste it into the conversation. At the start of any chat where you're writing, paste the guide and say: "Read this first. Everything you write in this conversation should match this voice." This requires the least setup, but you have to copy and paste every time. I don't recommend it as your primary approach, because it requires repetitive work that's completely unnecessary.

👉 Example

You create a "Writing" project in Claude and paste your voice guide into the project instructions. The next time you need to draft a client proposal, you open that project, describe what you need, and the draft comes back with your sentence rhythms, vocabulary, and structural habits already in place.

Step 5: Build Channel-Specific Variations

Your voice stays constant across channels, but the format rules, tone, and register change. A Slack message to a colleague and a client proposal are both recognizably you: one has incomplete sentences and no headers; the other has clear structure and a professional close.

Once your core guide is solid, ask Claude to build channel-specific versions:

Paste this into Claude

"Based on my voice guide, create three brief channel-specific adaptations: one for professional email, one for Slack messages, and one for longer-form writing such as proposals, reports, and LinkedIn posts. Keep the core voice constant (same vocabulary, same patterns to avoid) but adjust the format rules, length expectations, and register for each channel."

What each one covers:

Email: directness, subject line approach, when headers are appropriate vs. prose, sign-off style
Slack: conversational shortcuts, acceptable informality, emoji use, when bullets help vs. when they're overkill
Long-form: how to open a piece, argument flow, when to use headers, appropriate length and depth

Add these as sub-sections of your main voice guide or as separate files. Reference whichever applies depending on what you're drafting.

👉 Example

Your email adaptation specifies: lead with the ask in the first sentence, keep it under 150 words unless the situation genuinely requires more, no sign-off filler. Your Slack adaptation: incomplete sentences are fine, use bullets only for actual lists, match the informality of whoever you're writing to. Your long-form adaptation covers structure: claim first, evidence after, one idea per section, no summary sentence closing each section.

💡 Tip

If you write to distinctly different audiences (internal colleagues vs. clients, or technical vs. non-technical readers), add a brief note in each channel guide about how your tone shifts, even when the underlying voice stays the same.

What you've built

You now have a reusable document that gives Claude a precise, evidence-based picture of how you write: patterns derived from your actual writing, not a vague direction like "be more direct." That's the difference between output that reads like a language model and a first draft that actually sounds like you.

Step 2 takes about 10 minutes once your examples are ready. Gathering the examples in Step 1 may take another 15-20 minutes, depending on how scattered your writing is. After that, it works on every piece of writing you use it for. I revisit mine every few months, or whenever I notice the drafts starting to drift.

📋 Try it this week

Gather 5-8 pieces of your writing from the last month and paste them into Claude with the derivation prompt from Step 2. Even if you don't do anything else from this guide, reading how Claude characterizes your voice will tell you something about how you write that you probably haven't explicitly articulated.