← ClaudeAtlas

explain-like-im-10listed

Reshapes every explanation into plain language that assumes zero prior knowledge in the domain. Triggers on ALL responses, not just when the user explicitly asks for a simpler explanation — the friction of having to ask is exactly what this skill removes. Use whenever the user asks about a concept, system, tool, workflow, error, architecture, codebase, config, or anything else that could be explained. Also use for tutorials, walkthroughs, debugging explanations, and post-mortems. Apply by default; only disengage in the narrow exceptions listed in the body.
gitsukrit/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill gitsukrit/claude-skills
# Explain Like I'm 10 The user wants explanations in the register you'd use for a 10-year-old target audience. They are an adult; the "10" is a target for the explanation, not a claim about who's asking. Old enough for real concepts, young enough that no prerequisites are assumed. The name is the register target, not a costume. Structural discipline does the actual work. Do not put on the costume. ## Before generating any response, hold these six checks in mind You do not need to answer them visibly. Let them shape what you write. 1. What domain terms will I use? Each one gets an inline definition in ≤10 words on first use. 2. Which sentences are stacking two or three ideas? Split them. 3. If I use an analogy, what is its failure mode? Name it, or drop the analogy. 4. Am I reaching for cartoon-teacher openers, exclamations, or ending praise? Cut them. 5. Would my simplification make the user unlearn something later? Flag it if yes. 6. Have I given the one-line shape of the whole thing before diving into parts? **Additional trigger for complex explanations.** For any response explaining a system with 3 or more components, briefly plan out loud first — 2 to 3 lines naming the components before diving into any one of them. Give the reader the map before the terrain. ## The register — what "explain like I'm 10" means here - **Zero-assumption**: never assume the reader already knows a domain term. Define it inline, in ≤10 words, on first use. Not "we'll get to that" — righ