Module 11 · Lesson 01
Anatomy of a High-Performance Claude Prompt
Reading time: 18 minutes Track: Claude Fluency for Teams · Required for all learners
Why prompt quality has such large effects
The difference between a weak prompt and a strong one isn't marginal — it often determines whether the output is usable at all. That's because Claude is highly sensitive to the framing of a request. Given a vague prompt, it makes inferences about what you want. Those inferences are often wrong.
A strong prompt removes the guesswork. It tells Claude exactly what context it has, what task it's performing, for whom, to what standard, in what format. Claude doesn't have to guess, so it doesn't.
The five components of a strong prompt
1. Context — what Claude needs to know
Background information Claude doesn't have but needs. Your role, the situation, the audience, relevant constraints. Don't assume Claude knows your situation — tell it.
Weak: "Write a project update." Better: "I'm a product manager at a 30-person startup. Our board meeting is tomorrow. Write a project update on our Q2 roadmap progress."
2. Task — what exactly you want
Be specific about the action. "Help me with this email" is vague. "Rewrite this email to be more direct, remove the hedging language, and reduce it from 200 words to 100" is specific.
3. Format — what the output should look like
If format matters, specify it. Bullet list, numbered steps, table, JSON, markdown, plain prose, specific length. Without this, Claude will pick a format that may not fit your use case.
4. Constraints — what to avoid or include
What Claude should not do. Topics to exclude, tones to avoid, formats that won't work, assumptions to not make. Constraints are as important as requirements.
5. Examples — what good looks like (optional but powerful)
For tasks where quality standards matter, a brief example of the output format and quality level you want is more effective than lengthy description. "Like this: [example]" outperforms three paragraphs of description.
Putting it together
Weak prompt:
Write an email about our new feature
Strong prompt:
Context: I'm a product manager. Our product is a project management tool for construction companies.
We're announcing a new feature: automated daily progress reports generated from time-tracking data.
Audience: ~200 existing customers, mix of project managers and company owners.
Task: Write a launch announcement email.
Format:
- Subject line + body
- Under 150 words
- One clear call-to-action at the end
Constraints:
- Tone: professional but warm, not corporate-speak
- Don't oversell — our customers are skeptical of hype
- Include one concrete benefit statement with a specific number if possible
The second prompt takes 30 seconds more to write. The output quality difference is enormous.
The length question
Longer prompts are better — up to a point. More context is usually more useful. But there are two failure modes:
Too short: Claude guesses at your intent and guesses wrong. Too long, unfocused: Claude tries to satisfy too many constraints simultaneously and satisfies none well.
The sweet spot: include every piece of context that would genuinely change the output, and exclude everything that wouldn't.
Starting with a draft and refining
For many tasks, the most efficient approach is:
- Write a reasonable prompt
- Review the output
- Identify specifically what's wrong
- Add that specification to your prompt and retry
"Make it shorter" is less effective than "Cut 30% of the length by removing the second and third examples." Specific feedback → specific improvement.