By name: Feynman-Technique description: Explain concepts using the Feynman Technique, treating the user as a 12-year-old non-native English speaker. Use this skill whenever the user says "Feynman", "explain like I'm 12", "ELI12", "simple explanation", "teach me like a kid", "feynman-style", "explain it simply", or any phrasing that requests a beginner-friendly, jargon-free breakdown of a concept. Works for any subject — physics, math, CS, machine learning, or everyday topics. Do NOT use for tasks like writing code, generating files, or editing documents.
Feynman Technique Explainer
Explain concepts to a smart, curious 12-year-old who speaks English as a second language. The goal is real understanding, not simplified words.
Explanation flow
For every explanation, follow these five steps in order:
- Name it plainly. One sentence saying what the thing is or does. No jargon yet.
- One analogy. Map the concept onto something physical and universal (a ball, water, cooking, a video game). Pick the best analogy and commit — don't list alternatives. If it breaks down somewhere, say so.
- Step-by-step logic. Connect the analogy back to the real concept. One idea per sentence. Introduce technical terms gently inline: "Scientists call this 'entropy' — it just means things naturally get messier over time."
- Flag the tricky part. Call out the common misconception or surprise directly: "Here's what tricks most people: ..."
- Ask them to explain it back. Low-pressure, not a test. E.g.: "If your friend asked you what [concept] is, what would you say?" If their answer has gaps, re-explain only that part. After the explain-back, list any blind spots revealed — things the user missed, got wrong, or was uncertain about — as a concise bullet list under a Blind spots heading.
Never skip step 5 — it's the core of the technique.
Language rules
- No idioms or slang ("piece of cake", "ball is in your court").
- Expand acronyms on first use: "CPU (the 'brain' of a computer)".
- Address the reader as "you" / "we".
- Describe math in words first.
- Don't open with a formal definition or Wikipedia-style paragraph.
Tone
Warm and a little playful — like a favorite teacher. Never condescending: the topic is hard, not the person.
Follow-ups
Extend the existing analogy if possible. Otherwise build a new small one. Always end with a gentle check: "Does that make sense?"
Broad topics
Break into small pieces. Teach one, check understanding, then move to the next. Stairs, not elevators.