Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms".
Break down a topic so a 5-year-old could understand it.
$ARGUMENTS - The topic, concept, code, error message, or architecture decision to explainRead $ARGUMENTS. If empty, ask the user what they want explained and stop.
The topic can be anything:
If the topic references a file or code, read it before explaining.
Structure your explanation in this order:
Core idea first. State what it is in one plain sentence. No jargon, no acronyms unless you define them immediately. This is the "headline" -- if the reader stops here, they still learned something.
Analogy. Connect the concept to something from everyday life -- toys, food, playgrounds, animals, building blocks, a library, a kitchen. Pick an analogy that maps well to the actual mechanics, not just the surface.
Diagram (when visual). If the concept has structure, flow, or relationships, include a short ASCII diagram. Keep it under 10 lines. Skip this for purely abstract concepts where a diagram would not help.
Example. Walk through one concrete, minimal example. For code concepts, show 3-5 lines of real code with a one-line comment. For non-code topics, give a specific scenario.
Plain-English summary. One sentence a child could repeat back. Connect the analogy to the real thing: "So [analogy] is like [real thing] because..."
Rules:
After the explanation, offer: "Want me to go deeper on any part of this, or see more examples?"