How to Make Claude Stay on Brand

You can make Claude stay on brand with a short brand brief, a few real examples, and a place for both that Claude reads every time. Here is how to write the brief, where to keep the brief, and why a person still reads every draft.

To make Claude stay on brand, give Claude what you would give a new writer on your team. That means a short brief that describes your voice, the words you use, the words you avoid with what to say instead, and real examples of lines that sound like you. Keep the brief somewhere Claude reads before every draft, ask Claude to check each draft against the brief, and have a person approve the result before anything is published.

Claude follows a clear brief well. Claude cannot know your brand until someone writes the brand down, and Claude is not accountable for what you publish. The brief and the final call stay with your team.

Why does Claude drift off brand without a brief?

Without a brief, Claude writes in a capable, general voice. That voice works for a first draft, and the voice is wrong for a brand with a sound of its own.

Anthropic's prompting guidance compares Claude to a brilliant new employee who lacks context on your norms. The guidance says the more precisely you explain what you want, the better the result. A brand brief is that explanation, written once and reused in every draft.

What goes in a brand brief that Claude can use?

Keep the brief short enough for a person to read in a few minutes. Write the brief in the same plain style you want Claude to use, because Anthropic notes that the style of a prompt can shape the style of the reply.

• Describe the voice in a few plain sentences. Name your reader and what that reader should know or do after reading.

• List the words you use. Include product names spelled exactly, the terms your customers use, and the phrases that belong to your brand.

• Pair every word to avoid with what to say instead. Write "Say 'sign in' instead of 'log in'" rather than "Never say 'log in.'"

• Give the reason behind each rule. Anthropic's guidance says that explaining why an instruction matters helps Claude understand the goal and apply the rule to new cases.

• Add examples of on-brand and off-brand lines. Show a line that sounds like you, a line that does not, and the rewrite.

Why should every "avoid" in the brief come with a "use"?

Anthropic's prompting guidance recommends that you tell Claude what to do instead of what not to do. The guidance gives a formatting example: instead of "Do not use markdown," ask for "smoothly flowing prose paragraphs."

The same idea applies to brand voice. A list of banned words marks the edge of your brand, and a replacement shows Claude where the brand lives. Keep your avoid list and attach a replacement and a reason to each item.

How many examples does Claude need?

Anthropic calls examples one of the most reliable ways to steer Claude's tone, format, and structure, and recommends a few well-made ones. Make the examples relevant, so they come from your real channels. Make them varied, so Claude learns the voice instead of copying one format. A headline, a product description, an error message, and a social post make a good mix.

Here is the shape of one example pair for a payments product:

On brand: "Your payment is on its way. You'll see the money in your account by Friday."

Off brand: "Your transaction has been successfully processed and will be reflected in due course."

Why: We name the day because customers plan their week around payments.

When you paste examples into a prompt, wrap each one in a simple tag such as <example>. Anthropic recommends tags like these so Claude can tell your examples apart from your instructions.

Where should you keep the brief so Claude reads the brief every time?

Put the brief where Claude sees the brief without anyone pasting the text into each chat. The Claude apps offer more than one place, and the right choice depends on how your team works. Menus change, so look for these features by name.

A Claude Project keeps the brief with one body of work.

A Project is a workspace with its own chats and its own knowledge. Put the short rules in the project instructions, which apply to every chat in that Project. Upload the longer brand guide, the glossary, and approved samples to the project knowledge. On Team and Enterprise plans, you can share a Project with colleagues, so everyone drafts from the same brief.

A Skill carries the brief into any chat.

A Skill is a folder of instructions and resources that Claude loads when a task calls for the Skill. A Project keeps its context inside that Project, while a Skill works across chats and Projects. A brand Skill can hold the voice rules along with logo files, color codes, and approved fonts. You can describe the task to Claude and have Claude help you build the Skill. On Team and Enterprise plans, owners can make a Skill available to the whole organization.

How do you get Claude to check a draft against the brief?

Make the check its own step, so Claude has one job at a time. The order below works for a single post or a whole campaign.

1. Draft with the brief in place. Work inside the Project or confirm that the Skill is turned on.

2. Ask for a check against the brief. Have Claude list every word, claim, or sentence that departs from the brief, with the rule each one breaks and a suggested fix.

3. Read the list yourself. Accept the fixes that fit the brief and reject the rest.

4. Ask for the revision. Then give the revised draft to the person who approves your brand's copy.

Treat Claude's check as a second opinion. The approval belongs to a person.

What does a human review still catch?

A brief keeps the voice steady. The brief cannot tell Claude what is true about your product right now, what your legal team approved, or which promises your team can keep.

• Every fact and claim gets checked. Claude may write a confident detail that nobody decided, so trace each claim to a source your team trusts.

• The reader comes first. Read the draft as your customer would, including a customer who uses a screen reader or reads English as a second language.

• The brief improves after each review. When a reviewer fixes the same problem twice, add the rule, the replacement, and the reason to the brief.

I teach this in my Skillshare classes on AI-native design. The same brief-first habit helps with screens as well as words. For that process, read how to turn research into a clickable prototype with AI.

In short

• Write a short brand brief with your voice, your words, a replacement and a reason for every word to avoid, and real examples.

• Keep the brief in a Claude Project or a Skill, so Claude reads the brief before every draft.

• Ask Claude to check each draft against the brief, and have a person approve every piece before the piece is published.

If you'd like help building a brand brief that your team and Claude can both follow, explore AI-native product research and design.