Everyday Claude – Core Habits for Productive AI Work By the end of this lesson, students should be able to: 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: 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. A communications manager uses Claude to draft internal announcements but always finds them too polished and corporate-sounding for her company's casual culture. She adds one sentence to every announcement prompt: "Write this in a casual, direct tone as if a real colleague wrote it – not corporate newsletter voice." The first draft she receives now typically requires only minor personalization rather than a full rewrite of the tone. One constraint sentence, consistently applied, saves her fifteen minutes per announcement. You can add "Before you respond, ask me any questions you need to write this well" to a prompt when the task is complex and you are not sure you have given Claude enough context. Claude will ask clarifying questions rather than making assumptions – and the questions it asks often reveal what was missing from your original prompt. When writing prompts for sensitive professional content – HR communications, legal notices, client communications, financial summaries – always review the output for accuracy before use. Constraints in a prompt tell Claude what format to use; they do not verify that the content is factually or legally correct for your specific situation. Take a request you have recently made to Claude that produced an unsatisfying result. Rewrite it using all four components: context, task, format, and at least one constraint. Run the new version and compare. Document the specific changes you made and which component most improved the result. You should be able to identify all four components of a strong prompt, write a complete prompt for a real work task that includes all four, and explain why the format component is the most commonly missing one. Log in and enroll to access lesson quizzes.
Lesson 2: Writing Better Prompts from Day One
Lesson Objectives
Lesson Content
Practical Example
Lesser-Known Tip
Safety Notes
Practice Task
Completion Check