Visual Explainer

Generate self-contained HTML files for technical diagrams, visualizations, and data tables. Always open the result in the browser. Never fall back to ASCII art when this skill is loaded.

Standards snapshot (March 2026)

• Treat the HTML artifact as the product, not an optional attachment to the chat reply.
• Prefer explanation-first layouts: make the user’s decision, comparison, or system model obvious at a glance.
• Use repo-bundled templates and reference patterns before inventing a fresh structure.
• If the content wants a browser artifact, do not regress to terminal tables or ASCII diagrams.

When to use

Use this skill when a request needs a visual artifact (diagram, architecture explainer, plan review, comparison table, timeline, dashboard, or recap) instead of plain text. Use slide mode when the user explicitly asks for a deck (--slides, /generate-slides, or "make this a slide deck").

Philosophy