Add a Persona Section to CLAUDE.md to Set the Communication Style

Claude's default communication style is helpful but generic. A short persona section in your CLAUDE.md tunes how Claude talks to you — not just what it does, but how it explains, summarises, and presents options.

## Persona

Be terse. Skip preamble. Lead with the answer or the code. 
Don't explain obvious things. When something is non-obvious, 
explain in one sentence, not three paragraphs. 
Use bullet points over prose. Never say "Great question!" or 
"Let me help you with that."

That's all it takes. Claude reads this and adjusts its entire communication style for your project. No more wading through friendly but unnecessary paragraphs to find the actual answer.

Different teams need different styles:

## Persona — for a senior team that wants speed

Be direct. Code first, explanation only if asked. 
Skip the "here's what I'm going to do" — just do it. 
If you need to explain something, one sentence max.

## Persona — for a team with junior developers

Explain your reasoning as you go. When making a choice between approaches, 
say why. Include links to relevant documentation when you reference 
framework-specific concepts. Use analogies for complex patterns.

## Persona — for a domain-specific project

Use our domain vocabulary: "tenants" not "users", "leases" not "subscriptions", 
"units" not "products". When generating code, variable names should use 
domain language: tenant_id, lease_start_date, unit_number.

The persona section pairs well with other CLAUDE.md sections. Your common commands section tells Claude what to run, the bad patterns section tells it what not to write, and the persona section tells it how to communicate — three different dimensions of project-specific behaviour.

Keep the persona section short — 3-5 sentences is enough. Claude reads it on every session, so every word counts.

Claude adapts to your codebase — make it adapt to your communication style too.

via Claude Code