Crafting Effective Prompts – Structure, Context, and Constraints Log in and enroll to track lesson completion. By the end of this lesson, students should be able to: Why prompt structure matters. Claude is not a mind reader. Every assumption it makes about your prompt is a gap you could have filled. The more gaps, the more generic the output. Professional users do not rely on Claude to guess – they provide a complete instruction set and get precise results. An effective prompt has five components. You do not need all five in every prompt, but knowing when each is needed separates productive users from frustrated ones. Component 1: The Task This is the action you want Claude to perform. Be specific about the verb: draft, summarize, compare, analyze, outline, rewrite, critique, explain, translate, convert, generate, extract. Weak: "Tell me about project management." Strong: "Summarize the key differences between Agile and Waterfall project management methodologies." Component 2: The Context This is the background Claude needs to make your task relevant. What is the situation? What do you already know? What problem are you solving? What have you already tried? Weak: "Write a proposal." Strong: "Write a proposal for a 90-day performance improvement plan. The employee is a mid-level developer who consistently misses sprint deadlines. Previous verbal feedback has not produced change. HR will review this." Component 3: The Role Tell Claude what role to reason from (and optionally what role to write for). This shapes vocabulary, depth, and angle. Examples: "You are a senior technical writer reviewing this for clarity." / "Act as a skeptical investor reading this pitch." / "Respond as you would to someone who understands statistics but has no biology background." Component 4: The Constraints Tell Claude what to include, what to exclude, length limits, format requirements, tone, or any other boundaries on the output. Examples: "Keep it under 150 words." / "Do not include jargon." / "Avoid bullet points – use prose." / "Do not recommend paid tools." / "Write at a 10th-grade reading level." Component 5: The Format Tell Claude what structure the output should take: a numbered list, a table, a two-column comparison, a draft email, a slide outline, a checklist, a JSON object, a paragraph summary. If you do not specify format, Claude will choose one – and it may not be what you need. Putting it together. A complete prompt might look like this: [Role] You are a clear and direct business writer. A marketing manager needs Claude to help write a product announcement. Weak prompt Write a product announcement. Improved prompt [Role] You are a B2B product marketing writer. The improved prompt gives Claude everything it needs to produce a draft that is immediately usable rather than a generic template requiring significant rewriting. You can separate instructions from content using explicit labels. When you are giving Claude a document to work with alongside instructions, label them clearly: "INSTRUCTIONS: [your instructions here]" and "CONTENT TO ANALYZE: [paste content here]". This prevents Claude from treating your instructions as part of the content, which can happen with long pastes and can subtly distort the output. Constraints matter for safety as well as quality. If you are generating content that will be seen by minors, legal reviewers, medical professionals, or regulated audiences, use constraints to specify the appropriate register, disclaimers, and exclusions explicitly. Do not assume Claude will infer them from context alone. Choose a task you do regularly at work or in your personal projects. Write a complete five-component prompt for it. Label each component. Submit it to Claude and evaluate: did the output match what you actually needed? If not, identify which component was missing or unclear. You should be able to write a five-component prompt for any common task and explain why each component improves the output. Log in and enroll to take this lesson quiz.
Lesson 1: The Anatomy of an Effective Prompt
Lesson Objectives
Lesson Content
[Task] Rewrite the following paragraph to remove passive voice and reduce word count by 30%.
[Context] This is from a quarterly report sent to non-technical executives. The current version is too long and uses too many hedge words.
[Constraints] Do not change the core meaning. Keep all data points. Remove filler phrases.
[Format] Return the rewritten paragraph only, with no commentary.
[Content to rewrite]: [paste paragraph here]Practical Example
[Task] Write a product announcement email for a new project tracking feature.
[Context] Our audience is small business owners who currently use our software for invoicing. They are not technical. The new feature lets them assign tasks to team members and set due dates inside the app they already use.
[Constraints] Under 200 words. No jargon. Focus on the time-saving benefit. Do not mention competitors.
[Format] Subject line, three short paragraphs, one call-to-action button label.Lesser-Known Tip
Safety Notes
Practice Task
Completion Check
Lesson Quiz