Lesson Content

The four components of a strong prompt.

Strong prompts are not long – they are specific. Four components cover most of what Claude needs to produce a useful result:

1. Context: Who you are, what you are working on, and relevant background. Claude cannot see your inbox, your organization, or your job title. Tell it what matters.

2. Task: What you want Claude to do. Be concrete – "draft," "summarize," "compare," "explain," "review," "rewrite." Verbs that are specific produce better results than vague requests like "help me with."

3. Format: How you want the output delivered. Length, structure, tone, style. Without format guidance, Claude defaults to its own judgment – which may not match yours.

4. Constraints: What to avoid, what to limit, what matters most. Constraints narrow the search space for Claude and prevent it from producing technically correct but practically useless output.

The difference specificity makes.

Weak: "Help me write a performance review." Strong: "Write a performance review for a software engineer at the mid-level who has been strong on delivery but has struggled with proactive communication with stakeholders. Keep it around 300 words. Use the format: Summary, Strengths, Areas for Growth, Development Actions. Tone: honest but constructive."

Both take the same intent. One takes twenty seconds longer to write and produces something you can use immediately.

Format guidance – the most commonly skipped component.

Most prompts include context and task but omit format. This produces the most common Claude complaint: "The response was way too long" or "It gave me a wall of text when I wanted bullet points" or "It was too formal." These are format mismatches, not task failures. Adding two sentences of format guidance resolves most of them.

Format options to specify:

• Length (words, sentences, paragraphs, "fit on one slide")
• Structure (bullets, numbered list, prose, table, sections with headers)
• Tone (formal, conversational, direct, warm, neutral)
• Voice (first person, third person, from a specific role)
• What to omit (no preamble, no summary at the end, skip the disclaimer)

Iterating rather than starting over.

When a response misses, targeted feedback produces better results faster than re-writing the entire prompt. Describe specifically what is wrong and what to change: "The second paragraph is too formal – make it sound like a real person wrote it, not a corporate document" produces a better follow-up than starting a new conversation with a longer prompt.