How to Make Claude Sound Human and Match Your Voice

To make Claude sound human, give it examples of your own approved writing and explain the choices you want it to repeat. Then test a short draft and correct specific phrases, sentence shapes, and levels of formality rather than asking it to simply be more human.

You are building a usable voice profile: a short description of how you communicate with a particular audience. fenbs can keep that approved profile in Skills and prompts, so the next connected assistant can read the same instructions instead of guessing your voice again.

What should you give Claude before asking it to write?

1. Choose two or three short pieces you wrote and still like. Match the format you need: client emails for client emails, not a personal essay for a product update.
2. Remove private details and mark the pieces as style examples. Tell Claude that their facts, names, and promises must not enter the new draft.
3. Explain the new audience, purpose, and approved facts. State what the reader should know or do after reading.
4. Ask Claude to describe the writing patterns it sees, then approve or correct that description before requesting a full draft.

A useful sample shows actual decisions. Perhaps you begin with the request, explain the reason in one sentence, and end with a date. Another person may open with context and use a warmer closing. Neither is inherently more human. The useful question is which pattern sounds like you in this situation.

Anthropic recommends explicit constraints and relevant examples in its prompting guidance↗ (opens in a new tab). You can use that principle without knowing technical prompting terms: show the result you mean and explain the parts that matter.

How do you turn writing samples into practical rules?

Ask for observations you can check. “Warm and authentic” can mean almost anything. “Begin with the outcome, use everyday verbs, and keep the request in its own sentence” gives you something to accept or reject. Keep the profile short enough that you can notice when a draft breaks it.

• Opening: answer the reader’s main question before introducing background.
• Vocabulary: use the terms the reader already uses; explain an unfamiliar term when it is necessary.
• Rhythm: mix short and medium sentences rather than forcing every sentence to the same length.
• Tone: be friendly through useful details and respectful requests, rather than praise or exaggerated enthusiasm.
• Accuracy: preserve qualifications, dates, and ownership; do not add a personal experience to create warmth.

Say you manage a small design studio. An approved rule might be: “When a delivery date changes, state the new date, explain the cause once, and say what we need from the client.” That tells Claude more than “write like a real designer.” It also gives a teammate a standard they can review.

Keep that approved standard with the reusable prompt in fenbs Skills and prompts, so later edits refer to the same voice profile.

What prompt helps Claude match your voice?

Separate the samples from the new assignment so Claude has less reason to mix their content. A short label is enough. Put the approved rules above the task, then ask for a small test before a longer document. You can expand this pattern using our system prompt examples.

Use the samples below as evidence of my writing style, not as facts for the new task.

First list five observable style patterns. Ask me to approve the list.

Approved rules: [paste rules]
Audience: [reader and relationship]
Purpose: [what the reader should understand or do]
Facts allowed in this draft: [verified details]
Samples: [paste your approved writing]

After I approve the patterns, draft 150 words. Preserve the facts. Do not invent personal experience, quotes, or commitments. Return the draft without a preface.

If the result feels wrong, identify a sentence and describe the mismatch. “This sounds too formal because I would say ‘send’ rather than ‘provide’” teaches a clearer preference than “try harder.” Ask for the paragraph again with only that change, so you can see whether the instruction helped.

Why do words such as “genuinely” keep appearing?

A repeated word in your draft is a visible editing problem, not evidence of a motive. You do not need a theory about why Claude likes it. Search the draft for the word, ask what it adds in each sentence, and remove it where the meaning stays the same.

For example, “We are genuinely excited to share the revised layout” could become “The revised layout is ready for your review.” If excitement matters and you actually feel it, you can keep it. The test is whether the sentence communicates something true and useful to this reader.

Avoid replacing one repetitive habit with another. A giant forbidden-word list can turn every draft into a vocabulary puzzle. Add a short rule about the underlying problem, such as “state the news directly; avoid unnecessary intensifiers.” For editing a draft that already exists, use the separate guide to making Claude’s prose more natural.

Where should your voice instructions live?

Keep broad preferences separate from a client’s particular requirements. “Use plain English” may apply across your work. A client’s approved product terminology belongs with that project. A one-time instruction to write a formal notice belongs in the assignment itself.

Claude distinguishes account-wide instructions, project instructions, and skills in its personalization guide↗ (opens in a new tab). Choose the scope deliberately. A casual tone that works for your internal updates may be inappropriate for a letter to a regulator.

If you are still learning the product, start with what Claude is. For a writing workflow you are building into your own software, use our Claude API guide as the starting point. For broader instruction patterns, browse the AI prompts hub. Voice rules help writing sound consistent; they do not establish whether its claims are correct or remove your responsibility to review it.

How to do this with fenbs?

1. Create a free account and add a project for the writing you want to keep consistent.
2. Add the approved voice profile and the reusable task prompt to Skills and prompts. Use examples you have permission to share and remove sensitive details.
3. Record any continuing editorial choices you make in Decisions and rules. Keep a suggestion open until a person approves it.
4. Connect a supported assistant and ask it to read the project context and approved prompt before drafting. Review the output, then save useful corrections as lessons.

fenbs is not the right fit if you only need to revise one sentence or keep your writing inside Claude. It does not train Claude, import your chats, or guarantee a particular voice. Its role is keeping the approved instructions and work record available when sessions or assistants change.