eli5

{
  "name": "eli5",
  "description": "Build an interactive, self-contained HTML explainer that makes a hard idea genuinely click - a thing you operate, not a document you read. Lets the mechanism pick the shape of the page from eight that recur (Machine, Field, Solid, Ladder, Fork, Trace, Assembly, Reveal) rather than giving every topic the same tabs, and commits to a palette and type pairing of its own. Grounded in the cognitive science of how people form mental models: a structure-mapping analogy carrying the boundary where it stops being true, a Predict-Observe-Explain beat where the reader commits a guess before the reveal, and readouts inside the diagram rather than beside it. Inlines Three.js when a flat projection loses the invariant, GSAP when a state change moves several things in order or a Reveal scrubs on scroll, a Remotion-rendered clip when the sequence is too expensive to compute live, and generated imagery from media-gen-pro - all embedded, never from a CDN. Fails the build on an artifact that draws with SVG and CSS alone unless the choice is declared, since four in a row did. Ships a scaffold that wires the theme tokens, reduced-motion path, markers and libraries in one command, fetching each library once from a pinned checksummed URL rather than a CDN the reader would load. Routes charts through the dataviz skill first. A deterministic linter fails the build on external assets, missing viewBox, uncaptured pointer drags, leaked animation frames, motion with no reduced-motion path, buried analogy limits, absent prediction beats, thin visuals, single-mode interaction, prose over budget, condescending register and copied template headings. Use for \"/eli5 <topic>\", \"explain how X works\", \"make me an explainer for Y\", \"I still don't get Z\". Names its reader as a curious sixteen-year-old rather than a peer, and fails the build on a topic-specific term used without a definition - the failure a baby-talk detector cannot see - on placeholder nouns an