Visual Explainer

Core principle: when an explanation is structural, comparative, multi-part, or spatial, render it as an HTML page instead of paragraphs — and reach for it on your own, not only when asked.

When it fires

Apply one test: would a diagram beat prose here? Yes for architecture, data or control flow, before/after refactors, system and state-machine design, multi-step plans, tradeoff comparisons. No for short, simple, or factual answers — those stay prose. An explicit ask ("explain this in HTML", "show me a diagram") always fires. Don't gate on permission: when it applies, produce the page as part of answering. The chat reply still stands; the page supplements it.

Invariants