eli5-flowlisted
Install: claude install-skill prgmr99/eli5-flow
# eli5-flow
Explain the topic to someone who knows nothing about it, as a HTML artifact with big pictures and few words. Unlike a plain ELI5, the whole explainer is built around **one clear chain of causes and effects**.
Topic: $ARGUMENTS
Write in the language the user is using.
## Who it's for
Default: someone who knows nothing about the topic.
Switch to **dev** when the request asks for it — `--for dev`, `--for developers`, or plain words in any language ("for engineers", "개발자에게 설명해줘"). Take that part out of the topic before you explain it.
| | default | dev |
|---|---|---|
| Words | everyday words, no jargon | the real terms (DNS lookup, TCP handshake, reconciliation, commit) |
| Pictures | everyday analogies (a phone book, a letter) | the real parts (browser, server, DOM, the event loop) |
| Depth | why it happens | why it happens, and what actually does it |
| Easy to mix up | what a beginner gets wrong | what developers actually get wrong |
Everything else is identical: the same chain rules, the same snap-a-link, the same layout, the same number of cards. Only the words and the depth change — dev pages are not longer or busier.
## What matters most, in order
1. **The main flow is clear at a glance.** Reading only the cards, left to right, once, a beginner gets the whole story.
2. **Every link is true.**
3. **Extra detail** — only where it doesn't slow down #1 or make the page busier. When in doubt, leave it out.
## Workflow
1. Work out the chain first, follo