to-html

Swap the wall of markdown for one self-contained .html file. Plans, explainers, comparisons, maps, and post-mortems are spatial information that markdown flattens — a side-by-side, an annotated diff, or a clickable prototype turns something the reader would skim into something they actually read.

When

Reach for HTML when at least one is true; otherwise stay in chat:

• The answer compares things the reader needs to point at.
• It has spatial structure — maps, timelines, flowcharts, diagrams.
• It has interaction prose can't convey — easing, click-throughs, sliders, toggles.
• It will be returned to or handed off — status reports, design systems, plans, post-mortems.
• The user will edit it as part of their workflow — boards, editors, tuners. These always end with an export button.

Personality — theme to the context

No shared stylesheet; the subject dictates the look. A post-mortem reads like a serious report (restrained, near-monochrome, one alarm color); an architecture map like a blueprint (monospace labels, thin rules); an explainer editorial (serif headings, generous measure); a triage board like a tool (dense, utilitarian).