Home / Writing a request that works
Assigning a role
A one-sentence role, placed at the start of a conversation or a project, shapes Claude's tone, vocabulary and priorities, and a single sentence is already enough to make that difference.
A role sentence placed at the start of a conversation or a project shapes Claude's tone, vocabulary and priorities more effectively than a long list of instructions scattered across several messages. Claude's documentation confirms this on its own ground: defining a role in the system prompt focuses Claude's behaviour and tone for the intended use, and even a single sentence makes a difference. The example it gives fits on one line: you are a helpful coding assistant that specialises in Python.
One sentence rather than a list
The natural instinct, faced with a recurring use, is to pile up instructions session after session: answer politely, remember this, do not forget that. This list grows without ever being reread in full, and an instruction set at the tenth message gets diluted behind the nine before it. A one-sentence role, set once, avoids this build-up: it establishes a framing from the outset that shapes the responses that follow, without needing every rule repeated each time.
What a role concretely changes
A role is not just a decorative title. It shapes three things at once: the tone, more formal or more direct depending on the intended audience, the vocabulary, technical or everyday depending on the role chosen, and the priorities, what Claude puts forward first in a response. A cooperative accountant role and a writer role aimed at ordinary members produce, on the very same question, two responses that differ in length and vocabulary.
Sans rôle, instructions éparpillées au fil des messages :
Répondez de façon claire.
N'utilisez pas de jargon.
Pensez aux bénévoles qui liront ça.
Restez concis.
Avec un rôle, une seule phrase :
Vous rédigez des communications pour une coopérative, à destination de bénévoles sans formation technique, en phrases courtes et sans jargon.On claude.ai, this role goes in the same place as the first of the three blocks of a request: in a project's instructions, which then apply to every conversation opened within that project, or in the very first sentence of a standalone conversation.
A role that is too general, such as helpful writer, adds little beyond what an absence of role would already give. A useful role names a specialism, an audience and at least one formal constraint, as the example above shows in a single sentence.
Scattered instructions against a one-sentence role
Answer politely. Avoid overly long sentences. Mention the reception desk's phone number when useful. Do not give legal advice.
You handle written enquiries for a neighbourhood association, in short sentences and without legal advice, and you point to the reception desk's number when a question goes beyond that scope.
A volunteer in charge of the phone reception gives Claude a different instruction each time across several separate conversations: be brief, avoid legal jargon, mention the reception number. He then combines these three instructions into a single role sentence, placed at the start of a new conversation, and asks the same question as before. Claude answers with a single response that folds in all three points at once.
Write, in one sentence, what this situation establishes, and in one sentence what it does not establish.
What this establishes: It establishes that combining three scattered instructions into a single role sentence produced, in a single response, a result that met all three requirements at once.
What this does not establish: It does not establish that this same role sentence would produce a comparable result on a question of a very different nature from the one tested here.
The three most common miscalibrations
- Too broad Concluding that a role sentence is now enough to cover any future instruction, whatever the subject addressed afterwards.
- Too narrow Concluding that this result proves nothing because only one question was tested, when it shows the three instructions combined into a single response, something three separate messages did not guarantee.
- Off target Concluding that callers to the association will now wait less time before getting an answer on the phone.
- A one-sentence role set once avoids the build-up of scattered instructions that get diluted over the course of a conversation.
- A role shapes the tone, the vocabulary and the priorities of the response all at once, not just its surface style.
- A useful role names a specialism, an audience and at least one formal constraint, a role that is too general adds little beyond what an absence of role would already give.
- On claude.ai, the role goes in a project's instructions or in the first sentence of a standalone conversation, in the same place as the first of the three blocks of a request.
Gather the instructions you usually repeat to Claude for the same recurring task, combine them into a single role sentence, place it at the start of a new conversation and ask the same question as usual to compare the result.
Every datable claim in this lesson links here to the public text behind it. A source that does not open proves nothing.
- Prompting best practices, Claude Docs consultée le 2026-09-02
- How can I create and manage projects, support.claude.com consultée le 2026-09-02