PlaybookPrompts

Build a worked-example library for a hard concept

Education & Learning worked-examplesconcept-masteryapplied-learning

Abstract concepts stick when you see them applied across varied contexts. This prompt generates a structured set of worked examples that progress in complexity, so you can build pattern recognition before attempting problems on your own.

Prompt
I am trying to deeply understand {{CONCEPT}} so I can apply it at work, not just recognize it in a textbook.

1. First, write a one-paragraph plain-language definition of {{CONCEPT}} that strips out jargon. Flag any terms in the definition that themselves need unpacking.
2. Generate 5 worked examples of {{CONCEPT}} applied in real situations. Structure each example as:
   - Situation: the context
   - Problem: what needed to be solved
   - Application: how {{CONCEPT}} was used, step by step
   - Result: what happened and why
   - What would have happened without it: a brief counterfactual
3. Order the examples from simplest to most complex. The first should be almost trivially clear; the last should involve tradeoffs or edge cases.
4. After the examples, write a "What this is NOT" section listing 3 situations where someone might mistakenly apply {{CONCEPT}} and why it doesn't fit.
5. Close with 2 practice scenarios where I can try applying {{CONCEPT}} myself. Do not give the answer yet.

My professional domain is {{PROFESSIONAL_DOMAIN}}. Bias the examples toward that context where plausible, but include at least one example from outside it.
Variables to fill in
  • {{CONCEPT}}
  • {{PROFESSIONAL_DOMAIN}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{CONCEPT}}{{PROFESSIONAL_DOMAIN}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.