Concept Explainer
Overview
Make hard ideas click. Calibrate to the learner's level, build from what they already know, use a vivid analogy, then layer in precision and a concrete example. End by checking understanding.
Keywords: explain, ELI5, teach, understand, intuition, analogy, mental model, break down, simplify, deep dive, learning, tutoring.
Workflow
- Calibrate the level. Infer or ask the audience level: child / curious novice / practitioner / expert. Match vocabulary and assumed background. When unstated, default to "smart person new to this field" and offer to go deeper.
- Anchor to prior knowledge. Start from something the learner already understands and bridge to the new idea ("you know how X works? This is like that, except…").
- Lead with one strong analogy. Pick a single, accurate analogy (see techniques in
references/techniques.md). State where the analogy holds and, crucially, where it breaks down — bad analogies that aren't bounded create misconceptions.
- Give the precise definition after the intuition, not before. Intuition first, formality second.
- Show a concrete worked example. Make the abstract tangible with real numbers, code, or a scenario.
- Layer depth progressively. Structure as: one-sentence gist → short paragraph → deeper mechanics. Let the reader stop at the depth they need.
- Address the common misconception for the topic head-on ("A lot of people think X — actually…").
- Check understanding. End with a quick question, a "you'd now be able to…" statement, or an invitation to go deeper.
Decision Framework
| Audience |
Style |
| Child (ELI5) |
Everyday analogy, no jargon, short sentences, concrete objects |
| Curious novice |
Analogy + plain definition + one example; define each term once |
| Practitioner |
Less analogy, more mechanics, trade-offs, when to use it |
| Expert |
Skip basics; focus on nuance, edge cases, precise terminology |
Worked Example (explaining "database index", novice level)
Gist: An index is like the index at the back of a book — instead of reading every page to find a topic, you jump straight to it.
How it works: A database without an index scans every row to find matches (slow, like flipping through all pages). An index keeps a sorted lookup of a column's values pointing to the matching rows, so the database can binary-search instead of scanning.
Where the analogy breaks: unlike a book index, a database index has to be updated on every write, so it speeds reads but slightly slows inserts and uses extra storage.
Example: CREATE INDEX ON users(email) turns "find the user with this email" from scanning a million rows into a handful of lookups.
Check: Given that, why might you not index a column you rarely search but write to constantly?
See examples/explain-recursion.md for a multi-level explanation.
Best Practices
- Intuition before formality. Never open with the textbook definition.
- One analogy, well-bounded — and always say where it breaks.
- Use concrete numbers and scenarios, not abstractions piled on abstractions.
- Progressive disclosure: gist → detail → depth, so readers self-select.
- Define jargon the first time; don't assume.
- Confirm understanding instead of assuming it landed.
Common Pitfalls
- Jargon to explain jargon — circular and useless to a novice.
- Unbounded analogies that quietly create misconceptions.
- Wrong level — ELI5-ing an expert (condescending) or overwhelming a beginner.
- Definition dump with no intuition or example.
- No worked example, leaving the idea abstract.
- Sacrificing accuracy for simplicity to the point of being wrong — simplify, don't falsify.
1---2name: concept-explainer3description: Explains complex or technical concepts clearly at the right level for the audience, using layered depth, concrete analogies, worked examples, and checks for understanding — adapting from ELI5 to expert. Use this skill when the user asks to "explain X", "ELI5", "help me understand X", "what is X and how does it work", "explain this like I'm a beginner/expert", "break down this concept", or wants a confusing topic made intuitive. Works for technical, scientific, financial, or abstract topics.4license: MIT5---67# Concept Explainer89## Overview1011Make hard ideas click. Calibrate to the learner's level, build from what they already know, use a vivid analogy, then layer in precision and a concrete example. End by checking understanding.1213Keywords: explain, ELI5, teach, understand, intuition, analogy, mental model, break down, simplify, deep dive, learning, tutoring.1415## Workflow16171. **Calibrate the level.** Infer or ask the audience level: child / curious novice / practitioner / expert. Match vocabulary and assumed background. When unstated, default to "smart person new to this field" and offer to go deeper.182. **Anchor to prior knowledge.** Start from something the learner already understands and bridge to the new idea ("you know how X works? This is like that, except…").193. **Lead with one strong analogy.** Pick a single, accurate analogy (see techniques in `references/techniques.md`). State where the analogy holds and, crucially, **where it breaks down** — bad analogies that aren't bounded create misconceptions.204. **Give the precise definition** after the intuition, not before. Intuition first, formality second.215. **Show a concrete worked example.** Make the abstract tangible with real numbers, code, or a scenario.226. **Layer depth progressively.** Structure as: one-sentence gist → short paragraph → deeper mechanics. Let the reader stop at the depth they need.237. **Address the common misconception** for the topic head-on ("A lot of people think X — actually…").248. **Check understanding.** End with a quick question, a "you'd now be able to…" statement, or an invitation to go deeper.2526## Decision Framework2728| Audience | Style |29| --- | --- |30| Child (ELI5) | Everyday analogy, no jargon, short sentences, concrete objects |31| Curious novice | Analogy + plain definition + one example; define each term once |32| Practitioner | Less analogy, more mechanics, trade-offs, when to use it |33| Expert | Skip basics; focus on nuance, edge cases, precise terminology |3435## Worked Example (explaining "database index", novice level)3637> **Gist:** An index is like the index at the back of a book — instead of reading every page to find a topic, you jump straight to it.38>39> **How it works:** A database without an index scans every row to find matches (slow, like flipping through all pages). An index keeps a sorted lookup of a column's values pointing to the matching rows, so the database can binary-search instead of scanning.40>41> **Where the analogy breaks:** unlike a book index, a database index has to be **updated on every write**, so it speeds reads but slightly slows inserts and uses extra storage.42>43> **Example:** `CREATE INDEX ON users(email)` turns "find the user with this email" from scanning a million rows into a handful of lookups.44>45> **Check:** Given that, why might you *not* index a column you rarely search but write to constantly?4647See `examples/explain-recursion.md` for a multi-level explanation.4849## Best Practices5051- **Intuition before formality.** Never open with the textbook definition.52- **One analogy, well-bounded** — and always say where it breaks.53- Use **concrete numbers and scenarios**, not abstractions piled on abstractions.54- **Progressive disclosure**: gist → detail → depth, so readers self-select.55- Define jargon the first time; don't assume.56- Confirm understanding instead of assuming it landed.5758## Common Pitfalls5960- **Jargon to explain jargon** — circular and useless to a novice.61- **Unbounded analogies** that quietly create misconceptions.62- **Wrong level** — ELI5-ing an expert (condescending) or overwhelming a beginner.63- **Definition dump** with no intuition or example.64- **No worked example**, leaving the idea abstract.65- **Sacrificing accuracy for simplicity** to the point of being wrong — simplify, don't falsify.
JayRHa