The short version

A role is useful when the professional perspective changes what a strong answer looks like. It should identify the kind of work, the setting, and the priorities Claude should notice first. It should not be a fictional biography or a substitute for task instructions.

Role is a judgment lens

Two readers can examine the same document and notice different things. A project lead looks for blockers, decisions, dependencies, and owners. A commercial contract reviewer looks for ambiguous obligations, termination exposure, and items that need qualified human attention.

The document has not changed. The lens has.

A compact framework

Build a role from three elements:

  1. Role: What kind of assistant is needed?
  2. Domain: Which team, audience, or operating context matters?
  3. Priority: Which signals should receive attention first?

For example: You are a research synthesis assistant for a strategy team. Prioritize evidence quality, conflicting claims, and decision-relevant uncertainty.

This sentence gives Claude a useful orientation without adding unnecessary character details.

Role versus task

The role explains how to judge. The task explains what to do now.

After setting the role, still specify the material to examine, the result required, important constraints, and the output format. A role such as “expert analyst” provides little value when the prompt never defines the analysis or audience.

Weak and strong roles

Weak: You are a brilliant, world-class expert.

This adds prestige language but no decision boundary.

Stronger: You are a project-risk review assistant for senior managers. Focus on delivery blockers, dependencies, decisions, and items requiring escalation.

The stronger version changes what Claude should select and how it should communicate.

When role prompting helps

Use it when audience, risk priorities, domain vocabulary, tone, or decision criteria materially affect the answer. Skip it when the task is simple and the role would merely restate the instruction.

Practical checklist

  • Put the stable role in the system instruction when possible.
  • Keep it short enough to remain clear.
  • Name the operating context or audience.
  • State the priorities that should guide selection.
  • Follow it with a concrete task and output request.
  • Test whether removing the role changes the answer in a useful way.

Try it

Start with: “Review these customer interview notes and identify the important themes.” Write one role sentence that names the team and three priorities. Then write the task separately. If the role does not alter the expected judgment, make it more specific or remove it.