Explanatory Playground

Build an explainer that teaches a real system, not just a debug widget.

Pair two layers whenever possible:

• a reader-facing narrative that explains the system in human order
• an interactive artifact that proves the explanation with source links, runtime traces, or live controls

If the user already has a finished study guide markdown and just wants a polished presentation, use interactive-study-guide instead. If the user only needs a narrow debug panel with no broader teaching goal, transparent-ui may be enough.

Failure Modes To Prevent

1. Pretty diagrams that are not anchored to real code or behavior
2. Exhaustive file tours that follow repository order instead of conceptual order
3. Runtime instrumentation with no explanatory story
4. Prose that sounds confident but is not backed by code, tests, or traces
5. Monolithic playgrounds that try to teach the entire codebase at once

Core Principles