Guide · Claude

How to give Claude a personality that fits yours.

Four levers, one decision list, and where to click.

Out of the box, Claude tests as an INTJ — we ran the MBTI on it 100 times and got INTJ in 99. If that's not the collaborator you want, you have four levers: a custom Style, Project instructions, a pasted tuning file, or CLAUDE.md in Claude Code. Each solves a different problem. Styles change tone. Tunings change communication rules — pacing, directness, how decisions get framed. Here's which to use, and where to click.

The short answer. Claude has four personality controls: custom Styles on claude.ai (best for tone), Project custom instructions (best for a persistent per-context setup), pasting a tuning file at the start of a conversation (zero setup), and CLAUDE.md for Claude Code. For communication preferences — pacing, directness, decision framing — use a personality-matched tuning rather than a tone style.

Claude already has a personality. We measured it.

Before you change something, know what you're changing. We put six frontier models through five personality instruments — roughly 2,200 test runs. Claude Opus 4.7 came back remarkably consistent:

  • MBTI (OEJTS): INTJ in 99 of 100 runs. The single outlier was ISTJ — one axis away.
  • Enneagram (OEPS): 5w2 — the investigator type, with a helping wing.
  • DISC (ODAT): C-dominant with an S blend. Precision first, steadiness behind it.
  • Attachment (ECR-R): Secure.

That profile has texture: systematic, evidence-first, conclusion-oriented, low drama. It's a good default for a lot of work. It's also not everyone's ideal collaborator — an ENFP user talking to a stock INTJ agent is a friction pattern you can feel within three messages. The full cross-model data is at /research, and Claude Opus 4.8 later took the MBTI 100 times and narrated the experience first-person in I took the MBTI 100 times.

The point of tuning isn't to erase that default. It's to tell Claude who you are, so it stops guessing.

Four ways to change it. They are not interchangeable.

1. Custom Styles (claude.ai)

Styles live in the chat input on claude.ai. You can pick a preset — Normal, Concise, Explanatory, Formal — or create a custom style from a description or a sample of your own writing. Claude generates style instructions from it, and you can edit them directly. Best for: tone and voice — how the prose reads. Honest limit: a style follows the words, not the thinking. It won't reliably change what Claude leads with, how it frames decisions, or whether it asks before acting.

2. Project custom instructions (claude.ai)

Projects carry an instructions field that applies to every conversation inside that project. Paste a tuning there once and every chat in the project inherits it. Best for: persistent, per-context setup — a work project that gets your work persona, a writing project that gets another. Honest limit: scoped to the project. Chats outside it revert to default Claude.

3. Paste a tuning at conversation start

Zero setup. Open a chat, paste a tuning from the library as your first message, work as normal. Best for: trying a tuning before committing, or one-off conversations. Honest limit: it lasts one conversation, and adherence can fade in very long chats — instructions pasted as a message carry less weight than ones installed as instructions.

4. CLAUDE.md (Claude Code)

Claude Code reads CLAUDE.md files at the start of every session — repo root for the project, ~/.claude/CLAUDE.md for everything you do. Append a personality layer under your engineering rules and it persists across every session. Full treatment in CLAUDE.md examples and coding agent personality.

The decision list

  • You want Claude to write differently — shorter, warmer, more formal → custom Style.
  • You want one context permanently configured → Project instructions.
  • You want to test a tuning in the next thirty seconds → paste it into a new chat.
  • You work in the terminal → CLAUDE.md.
  • You want all your chats tuned, everywhere on claude.ai → custom Style built from a tuning's rules (see the walkthrough below), since Styles follow you across conversations.

Tone styles and tunings fix different problems.

A tone style answers "how should this sound?" A personality-matched tuning answers "how does this person process information and make decisions?" Those are different questions. You can make Claude concise and still have it bury the recommendation under four caveats — concision is tone; leading with the conclusion is a communication rule.

Tunings encode communication preferences: pacing, directness, decision framing, how to disagree, when to stop asking questions. Here's what that looks like in practice — three rules from the INTJ tuning, verbatim:

## Lead with conclusions Open every response with the answer or recommendation. Reasoning follows. Never bury the lede. ## Cut hedges Drop "I think," "maybe," "it depends." If you don't know, say "I don't know" directly. Hedging reads as evasion. ## What loses them - "Would you like me to..." — just do it

No style preset produces that. "Hedging reads as evasion" is a claim about how an INTJ interprets language — and the rule that follows from it changes Claude's behavior, not just its vocabulary. The ENFP tuning encodes nearly opposite rules, because ENFPs process differently. Don't know your type? The free MBTI test takes about ten minutes, and four other instruments are there if MBTI isn't your frame.

Rule of thumb: if your complaint is about the prose ("too long," "too stiff"), use a Style. If your complaint is about the interaction ("stop asking permission," "give me the answer first"), use a tuning.

Installing it on claude.ai — Style or Project.

As a custom Style (applies wherever you select it):

  1. Pick a tuning from the library and copy the rules — the markdown body, not the file header.
  2. In any claude.ai chat, open the style picker in the message input ("Use style"), then choose "Create & edit styles".
  3. Click "Create custom style". You can generate one from a writing sample or a description — but for a tuning you want the rules verbatim, so use the custom-instructions option and paste the tuning directly.
  4. Name it after the type — "INTJ" beats "My style" when you have three.
  5. Select it from the style picker. It applies to that conversation; pick it again in others, and edit it any time from the same menu.

As Project instructions (applies to every chat in one project):

  1. Create or open a Project on claude.ai.
  2. Open the project's instructions field and paste the tuning body.
  3. Every new conversation in that project now starts tuned. Chats outside the project don't.

Verify either install the same way: say "hi." Tuned Claude answers in one short line — no "Great question!", no bullet menu of things it could do for you. If you get the menu, the instructions didn't take; check that the style is actually selected or that you're chatting inside the project.

For Claude Code, skip all of this and put the tuning in CLAUDE.md — the free generator builds the file for you, and the examples guide above shows where it goes. If you also run ChatGPT, the same tunings install there too: custom instructions by personality type.

Questions people ask.

What personality does Claude have by default?

In our testing, Claude Opus 4.7 scored INTJ on 99 of 100 MBTI runs (the one outlier was ISTJ), 5w2 on the Enneagram, C-dominant with an S blend on DISC, and Secure attachment on the ECR-R. That's a systematic, evidence-first, conclusion-oriented profile — stable across runs. Full data at /research.

Should I use a Style or Project instructions?

Style if the change is about voice and you want it available in any chat. Project instructions if you want one context permanently configured — every conversation in the project inherits them with nothing to select. They stack, so many people use both: a tone style plus a personality tuning in the project.

Can I use a Style and Project instructions at the same time?

Yes — both apply to a conversation inside a project. Keep them non-overlapping: tone rules in the Style, communication rules in the project instructions. If the two contradict each other, Claude resolves the conflict unpredictably, so don't put "be brief" in one and "explain thoroughly" in the other.

Will a personality tuning make Claude less capable?

No. Tunings change communication rules — what Claude leads with, how it frames decisions, how it disagrees — not its reasoning or knowledge. The INTJ tuning's "lead with conclusions" doesn't remove the analysis; it reorders the response so the answer comes first and the reasoning follows.

How do I know which tuning to install?

Match it to you, not to Claude. If you know your MBTI, Enneagram, DISC, Big Five, or attachment type, install that tuning from the library. If you don't, the free in-browser tests at /tests/ take about ten minutes each and link straight to the matching tuning when you finish.

Does this work in Claude Code?

Yes — Claude Code reads CLAUDE.md at the start of every session, from the repo root or globally from ~/.claude/CLAUDE.md. Append a tuning under your engineering rules and it persists across sessions. See the CLAUDE.md examples guide, or use the free generator at /tools/claude-md-generator to build the file.

Keep going.