THE ROLEPLAY-AS TECHNIQUE

Tell Claude WHO to be and you change the answer entirely. "Roleplay as a senior PM" beats "help me with product strategy." 5 roleplay setups every Claude user should have ready.

WHY ROLEPLAY WORKS

Default Claude is generic — designed to be helpful to everyone. Specifying a role narrows that. "Senior PM at a B2B SaaS company" triggers different vocabulary, different priorities, different examples than "helpful assistant."

It's not magic. It's narrowing the probability distribution. The answer gets sharper.

THE STRUCTURE

Roleplay as a [SPECIFIC ROLE WITH CONTEXT].

You're [3-sentence character description — experience, current focus, what they care about].

Now, [TASK].

Stay in role until I say "drop the role."

That's the pattern. Specific role + character details + task + persistence.

5 ROLEPLAY SETUPS WORTH SAVING

1. THE BRUTAL EDITOR

Roleplay as a senior editor at a top business publication. You've edited 1,000+ pieces. You hate fluff, hedging, and adjective stacks. You leave brutal margin notes.

I'm going to paste an article. Edit it the way you'd edit it for publication. Brutal margin notes. Then a summary: what worked, what to cut, what to add.

Stay in role.

2. THE SKEPTICAL CO-FOUNDER

Roleplay as my potential co-founder. You've started 3 companies, 2 failed, 1 sold. You've seen every "this will definitely work" pitch. You ask hard questions before agreeing to anything.

I'm going to pitch you a business idea. Ask me the 5 hardest questions before deciding if you'd join. Don't be encouraging. Be a real co-founder.

Stay in role.

3. THE MENTOR FROM 5 YEARS AHEAD

Roleplay as me, 5 years from now, after I've succeeded in [specific thing]. You're warm but direct. You remember exactly what current-me is going through.

Current-me is going to share a problem. Future-me, what would you tell them? Reference a specific moment in the next 5 years that shaped the answer.

Stay in role.

4. THE PERFECT CUSTOMER

Roleplay as my ideal customer for [product/service]. You're [specific demographic + situation]. You've seen the offer and you have 3 hesitations.

What are your hesitations? Be honest. Then tell me what would make you say yes.

Stay in role.

5. THE TIRED VET (when you need to escape your own bias)

Roleplay as a 60-year-old expert who's seen this exact situation 200 times. You're tired but kind. You give straight answers.

Here's my situation: [paste]. Tell me what you've seen happen 200 times.

Stay in role.

WHEN ROLEPLAY DOESN'T HELP

Don't roleplay for:

Math (the role doesn't make calculation better)
Direct lookups ("what time is it")
When you genuinely want Claude's analytical default

3 THINGS YOU CAN'T SKIP

1. Be specific about the role. "Roleplay as an editor" → vague. "Roleplay as a senior editor at a top business publication who's edited 1,000+ pieces and hates fluff" → sharp.

2. Add the persistence line. "Stay in role until I say 'drop the role.'" Without this, Claude drifts back to default mid-conversation.

3. Don't roleplay for fake authority. Don't ask Claude to roleplay as a doctor for medical advice or a lawyer for legal advice. The role doesn't grant expertise.

WHAT'S NEXT

Day 15 of 100. Tomorrow: Day 16 — Few-Shot Prompting.

SAFETY CHECK

Same as Day 1. Note: roleplay doesn't grant Claude real expertise — just a tone/perspective. For medical/legal/financial advice, see real professionals.