"Act As" and the Persona Family

"Act as a senior editor." "You are a UX researcher." "Pretend you're a historian." "Explain it like I'm 10." These are all the same move: assigning the model a character. Sheet 1 looked at one version of it (the expert claim); this is the whole family.

The common move

The familiar prompt Act as an experienced copy editor. Also, explain your changes like I'm 10 years old.

Assigning a role feels like summoning a specialist, and asking for a child's-level explanation feels like a shortcut to clarity. Both are personas. The question worth asking: what does a persona actually change?

What you think it does, and what it actually does

What you think it does

Grants the role's ability. "Act as an editor" feels like it makes the model an editor.
"Like I'm 10" buys clarity. Feels like the fastest route to a simple explanation.
More detail, better role. An elaborate backstory feels like a sharper specialist.

What it actually does

Shifts register, not capability. You get an editor's vocabulary and tone. The underlying ability is the same with or without the costume.
Often buys condescension. "Like I'm 10" tends to oversimplify and talk down, performing simplicity rather than achieving clarity.
Adds noise past a point. Extra backstory is more text to reconcile, not more skill.

This is the same lesson as sheet 1, generalized: a persona is a register tool. It changes how the model talks, not what it knows or can do.

The more honest move

Name the behavior you actually want, not the character you want it to wear. The costume is a vague proxy for the behaviors underneath it, so ask for those directly.

Behavior instead of costume Review this copy. Flag unclear sentences, passive constructions, and places where I've buried the point. For each, explain the problem in plain language with no jargon, using a short concrete example.

Notice what replaced what. "Act as an editor" became the specific editorial behaviors you wanted. "Explain like I'm 10" became its actual ingredients: plain language, no jargon, concrete examples. You get the clarity without the talking-down.

Try this

When you reach for "act as [role]," pause and ask: what do I actually want this role to do?

List those behaviors and ask for them directly. The persona was always just shorthand for them.

Keep the persona only when register itself is the goal (a tone, a voice, a vocabulary). For anything else, name the behavior.

The principle underneath

A persona changes how the model talks, not what it can do. Name the behavior you want, not the character you want it to play.