Most “explain this” prompts produce middle-school-depth explanations that bore advanced readers and confuse beginners. The depth has to match the reader, and the angle has to match what’s actually confusing — a definition won’t fix a missing intuition, and an analogy won’t fix a missing prerequisite. These prompts hit specific depths and specific failure modes. For the long-form workflow, see how to use AI to explain a difficult concept.
Best for
- Learning a new technical field
- Cross-discipline study (CS reading bio, lawyer reading ML)
- Teaching prep and lecture writing
- Demystifying jargon in a paper or doc
- Onboarding into a new codebase or domain
1. ELI5 (truly)
Explain {concept} to a smart 8-year-old. Use exactly 1 analogy from their world (school, playground, video games). ≤120 words. Avoid all jargon, even "easy" jargon like "algorithm" or "function". End with one sentence the kid could repeat to a friend.2. ELI undergrad (foundational)
Explain {concept} to an undergrad who has foundation in {prereq field} but no exposure to {concept}. Build from what they already know. State which prerequisite each step rests on. ≤250 words. Include 1 minimal worked example.3. ELI PhD (peer-level)
Explain {concept} at a graduate / research level. Skip basic definitions. Focus on: (1) where the field currently disagrees, (2) recent advances in the last 3 years, (3) the open questions a new researcher could attack. ≤300 words. Cite named approaches, not vague "researchers think".4. 3-depth ladder
Explain {concept} three ways: (1) one sentence the layperson gets, (2) one paragraph an undergrad gets, (3) one page an expert finds useful. Each layer builds on the previous without repeating it. Label each layer's intended reader.5. Analogy + caveats
Explain {concept} using a single strong analogy. Then state 3 places where the analogy breaks down and what reality does instead. Reader: smart adult with no field background. Goal: they leave with intuition that won't mislead them later.6. Compare to a similar concept
Explain {concept-A} by comparing it to {concept-B} (which I already understand). Format: (1) where they're alike, (2) where they differ, (3) the diagnostic question that tells you which one applies in a given situation. ≤300 words.7. Historical trace
Explain {concept} by tracing how it evolved: (1) the original problem people were trying to solve, (2) the first attempts and why they failed, (3) the key breakthrough and what it changed, (4) the current understanding. ≤400 words. Name the people or papers where they matter.8. Spot-the-flaw quiz
Explain {concept} in a 200-word block that contains exactly 1 deliberate flaw or oversimplification. End with: "Where is this explanation wrong or misleading?" Wait for my answer, then reveal the flaw and the correct version.9. Two-expert dialogue
Stage a 6-turn dialogue between two experts who disagree about {concept}. Expert A holds the {mainstream / orthodox} view; Expert B holds a {contrarian / heterodox} view. Each turn ≤40 words. They should clarify the real disagreement, not strawman each other.10. Pre-mortem misconceptions
List the 5 most common misconceptions a newcomer holds about {concept}, ranked by how badly each one breaks downstream understanding. For each: state the misconception in 1 sentence, then state the corrected mental model in 1 sentence.11. Worked example backwards
Explain {concept} by starting from a fully worked numerical or concrete example, then peeling back to the general principle. Reader: someone who learns better from examples than definitions. Show the example first, then label which part of it generalizes.12. Tiered Q&A drill
Generate a 5-question Q&A drill on {concept}, ordered from easiest to hardest. Question 1 = recall. Question 2 = comprehension. Question 3 = application. Question 4 = analysis. Question 5 = edge case / open problem. Include answers in a separate block.Common mistakes
- Defaulting to middle-school depth regardless of reader
- Dumping jargon without grounding it in something the reader already knows
- Skipping analogy when one would do the job
- Using an analogy without flagging where it breaks
- Treating “explain” as “define” — definitions don’t build intuition