Master Claude: Your AI-Powered Work Assistant / Projects and prompting
Effective prompting
About 12 minutes
A prompt is a brief. Anthropic's own prompting guide offers a simple test: show your prompt to a colleague who knows nothing about the task. If they would be confused, Claude will be too.
This lesson turns the main techniques from that guide into a checklist you can use every day.
The five-part brief
Most good prompts contain these parts:
- Task: what you want produced.
- Context: who it is for, why it matters, what Claude needs to know.
- Inputs: the material to work from.
- Constraints: length, tone, things to avoid.
- Format: exactly how the answer should look.
Example:
Task: Write a product description for our online shop.
Context: The buyer is a parent shopping for a child's first bike. They care about safety and ease of use more than speed.
Inputs: 16-inch wheels, removable stabilisers, hand brakes sized for small hands, weight 7.5 kg, ages 4 to 6.
Constraints: 80 to 100 words. No claims we cannot prove, such as "safest bike". UK spelling.
Format: One heading, one paragraph, then three bullet points.
Technique 1: Be clear and direct
Say exactly what you want. If you want more than the bare task, ask for it. The guide's example contrasts "Create an analytics dashboard" with a version that asks for more features and detail. Claude does not guess at ambition. You set it.
Technique 2: Give the reason
Instead of "NEVER use ellipses", the guide suggests explaining that the text will be read aloud by a text-to-speech engine that cannot pronounce them. With a reason, Claude can apply the rule sensibly in cases you did not mention.
Keep sentences under 20 words, because many of our readers use English as a second language.
Technique 3: Use numbered steps when order matters
1. Read the meeting notes below.
2. List every decision made.
3. List every action, with the owner's name.
4. Flag any action that has no owner.
Technique 4: Give Claude a role
A single sentence can focus tone and judgement.
You are an experienced bookkeeper who explains things to small business owners without jargon.
Technique 5: Put long material first, question last
The guide recommends placing long documents near the top of the prompt and your question at the end. When you paste a long report, put the report first and your instructions after it.
Technique 6: Ask it to check its work
Before you give the final answer, check it against my constraints and list any you could not meet.
This makes gaps visible instead of hidden.
A before-and-after
Weak:
Summarise this report.
Strong:
<report>
[paste report here]
</report>
I am a busy café owner. Summarise this report in five bullet points that affect my business. Then list anything in the report I must act on before the end of the month. If the report does not say something clearly, write "not stated" rather than guessing.
The last sentence matters. Telling Claude it may say "not stated" reduces the pressure to fill gaps with guesses.
Common mistakes
- Writing in shouty capitals. Calm, specific reasons work better than "IMPORTANT!!!".
- Hiding the real goal. If the summary is for a bank manager, say so.
- Forgetting the format. You then spend time reformatting by hand.
- Asking ten things at once. Split big jobs into steps (see Lesson 9).
Exercise
- Take a prompt you used in Lesson 2.
- Rewrite it with all five parts of the brief.
- Add one reason and one self-check line.
- Run both versions in fresh chats and compare. Write two sentences on what changed.