The Building Blocks of an Effective Prompt
CoreWrite effective, well-structured prompts · Difficulty 1/5
Explanation
Treat Claude Like a Capable New Colleague
A strong prompt gives Claude the same things you'd give a capable new colleague: what you want, why, for whom, and in what form. Official prompting guidance emphasizes being explicit and specific rather than terse.
The Reliable Building Blocks
| Element | What it does | Example phrasing |
|---|---|---|
| Task / goal | States exactly what to produce | "Draft a 150-word customer apology email." |
| Context | Background the model can't infer | "The customer's order arrived two weeks late." |
| Audience & tone | Shapes register and vocabulary | "For a frustrated enterprise client; warm but professional." |
| Format | The shape of the deliverable | "Use three short paragraphs, no bullet points." |
| Constraints | Boundaries and must/must-nots | "Do not offer a refund; offer a 15% credit." |
| Examples | Show the pattern you want | "Match the style of this past email: ..." |
Positive Framing and Placement
Prefer positive instructions ("write in plain language") over long lists of prohibitions -- a positive instruction tells Claude what to do, while a list of "don'ts" only narrows the space without pointing at the target. Also put the most important instruction close to the actual task rather than burying it in a long preamble.
When a past output was well-received, reusing it as an example ("match this style") is one of the most effective ways to steer tone and format on a new request -- it shows the pattern instead of describing it in prose.
Common exam traps
- "A shorter prompt is always better." This is false. Vague, under-specified prompts are the most common cause of weak output. Specificity beats brevity -- a longer prompt that spells out task, context, audience, and format will usually outperform a terse one.
- Assuming that adding more words automatically makes a prompt clearer. Clarity comes from covering the right elements (task, context, audience, format, constraints), not from length alone.
Key Takeaways
- Give Claude what/why/for whom/in what form, the same way you'd brief a capable new colleague
- The core elements are task, context, audience & tone, format, constraints, and examples
- Positive instructions beat long lists of prohibitions; put the key instruction near the actual task
- Reusing a liked past output as an example is a highly effective way to steer style and format
- A shorter prompt is not automatically better -- under-specification, not length, is the usual cause of weak output
Glossary Terms
Related Concepts