We rebuilt PromptSewa — and your prompts were reset

Lesson 3 · 5 min

Role, audience and context

A role is shorthand for a set of decisions. Use it to constrain judgement, not to flatter the model.

A role prompt tells the model which body of judgement to apply. "You are a copy editor" implies rules about clarity, repetition and tone. "You are a tax accountant writing for a small business owner" implies accuracy, plain language and a bias toward caution. Used well, a role compresses dozens of constraints into one line. Used badly, it becomes theatre: a paragraph of praise that changes nothing except the length of the answer.

Roles are decision shortcuts

Think about what decisions you want made in a particular way. Should the model assume the reader is technical? Should it refuse to speculate? Should it favour brevity over completeness? A role is a compact way to set those defaults. The test is simple: if you delete the role, does the output change in a way you can describe? If not, the role is decoration and you can spend those tokens on a constraint instead.

Audience is the sharper tool

If you only keep one of the two, keep the audience. A reader is concrete: a first-time user, a finance lead, a developer skimming a changelog. Audience controls vocabulary, sentence length, how much background is assumed, and which examples land. A role says who is speaking; an audience says who must understand. Most communication failures are audience failures, and a model with no stated audience defaults to a generic, middle-of-the-road reader who does not exist.

Example: "You are a technical writer explaining a database migration to a team that has never run one. Assume they know SQL but not our deployment process." The role sets the voice; the audience sets the depth; the second sentence tells the model what not to explain.

Context should be the material, not the mood

When people add context they often add atmosphere: "this is really important", "take your time", "do your best". None of that is information. Material context is the document, the data, the prior decisions, the house style. Paste the thing you want worked on. Name the constraint you keep having to repeat. If a colleague would need it to do the task, the model needs it too.

Where roles go wrong

Two failure modes are common. The first is a role that fights the task — asking for blunt feedback while instructing the model to be supportive produces hedged, useless notes. The second is a role that invites invention: "you are a world-famous expert" often produces confident generalities. Prefer a role that describes a job over one that describes a reputation.

Checklist

  • Does the role change a decision you can name?
  • Is the audience stated in concrete terms?
  • Is the context material you would hand a colleague?
  • Do the role and the constraints agree with each other?

Finished this lesson?

Mark it complete to generate a certificate you can print or save as a PDF. We ask for an email only so you can be reached — no account is created.

All lessons