/explain-to-me — rich HTML explainers

Turn a topic into ONE self-contained HTML file, Claude-branded, using the best-fit bundled template, then publish it and return a shareable URL.

Explainers are read-only by default. When the page's job is to get a decision made, add interview-style questions that record answers server-side — see references/decisions.md and step 4b.

Fixed constraints (do not violate):

• Palette is fixed: #FAF9F5 ivory, #141413 slate, #D97757 clay, #E3DACC oat, #788C5D olive. Do not rewrite CSS variables unless the user explicitly asks for a different look.
• ONE template per output. Never merge two templates.
• Static HTML only — inline <style> + inline <script>. No framework, no build. (User wants React → that's frontend-engineer, not this skill.)
• Strip regions you can't fill with real content. A 3-section real explainer beats a 7-section half-fake one.
• Never invent file paths, line numbers, or commit hashes to fill a citation region — drop the region instead.

When NOT to use