KeyanVakil/explain-like-im-five

Explain the target code or concept as if the listener is a smart but non-technical person encountering this for the first time.

Steps

1. Read the target code, file, or section being asked about.
2. Identify the core job it does in one sentence — start there.
3. Build up the explanation in layers:
   • What problem does this solve?
   • What goes in, what comes out?
   • What are the key moving parts and how do they relate?
   • What would break if this didn't exist?
4. Use analogies from everyday life. No jargon unless you immediately define it.
5. If there are surprising or non-obvious design decisions, call them out and explain why they exist.

Rules

• No "simply", "just", "obviously", or "as you know"
• Lead with the big picture before the details
• If it's genuinely complicated, say so — don't oversimplify to the point of being wrong
• End with one concrete example of the code in action

Output format

Plain paragraphs. Short sentences. No bullet soup unless listing truly enumerable things.