Claude Prompting Best Practices
Last reviewed
Correct answer: D. Iterate and refine the request based on what was produced
Explanation
Read what came back as evidence about the prompt. A first response that misses usually tells you which part of the request was under-specified: too generic means you set no constraints, off-topic means the goal was never stated, the wrong shape means the format was left open. Change that one thing and ask again.
That is different from sending the identical prompt a second time, which is the move people actually reach for. The same request carries the same information, so you are re-rolling rather than correcting, and any improvement is luck you cannot reproduce.
Anthropic's own advice is to start simple and add complexity only where it is needed, checking each addition to see whether it actually helped. In practice that is two or three rounds: supply the missing constraint, then an example if the shape is still wrong, then split the task if it was doing too much at once.
The useful test on a prompt that keeps failing is whether a colleague with no context could follow it. If they could not, the model cannot either.
Sources
“Show your prompt to a colleague with minimal context on the task and ask them to follow it. If they'd be confused, Claude will be too.”
“Start simple and add complexity only when needed. Test each addition to see if it actually improves results.”
Practise 5 questions on this topic
Take Claude Prompting Best Practices — Timed Test (5 questions) — scored instantly, explanation for every question, no login.