daBongo LMS AI Training Courses

Lesson Content

Context tells Claude why you are asking.

Context is the background that makes your request specific. Without it, Claude answers the general version of your question. With it, Claude answers your version of your question.

Think of context as answering: Who am I? What situation am I in? What do I already know? What have I already tried? What is this for?

You do not need to share your entire life story. You need to share the relevant facts that change how a good answer should look.

What counts as relevant context:

• Your role: "I'm a first-time manager dealing with a performance issue"
• Your current knowledge level: "I understand Python basics but have never used async/await"
• Your constraint: "I have a $500 budget"
• Your audience: "This will be read by people who have no IT background"
• Your goal: "I need to decide between two vendors by Friday"
• What you have already done: "I've tried restarting the service and checking the logs"
• What you do not want: "I've already decided not to use Salesforce"

Constraints are as important as instructions.

A constraint tells Claude what not to do, what to avoid, and what limits to respect. Constraints prevent Claude from producing technically valid but practically useless output.

Common constraint patterns:

• Length: "Under 200 words" / "No more than five bullet points"
• Tone: "Professional but not stiff" / "Direct, no filler phrases"
• Exclusions: "Do not recommend paid tools" / "Do not include generic advice"
• Format restrictions: "No tables" / "Prose only, no bullet points"
• Audience restrictions: "Assume zero technical knowledge" / "Write for a 12-year-old"
• Scope restrictions: "Focus only on the onboarding phase, not retention"

Negative constraints are underused and undervalued.

Telling Claude what NOT to include often produces more improvement than adding more positive instructions. If you consistently get outputs full of generic filler advice, "avoid generic advice" is a powerful constraint. If you keep getting long preambles before the answer, "skip the preamble, start with the answer" is a constraint that immediately improves your output.

Stacking constraints without conflicting them.

You can stack multiple constraints, but watch for conflicts. "Write in a casual tone" and "use formal academic language" will produce confused output. "Under 100 words" and "include a detailed section on each of five topics" is arithmetically impossible. When Claude produces something strange, look for conflicting constraints in your prompt first.