to-html

Produce a single-file HTML artifact instead of a wall of markdown when the answer is spatial, side-by-side, interactive, or live-rendered — letting the reader see it at a glance rather than reconstruct it from prose. Use this skill whenever the user asks for an explanation, plan, design exploration, code review, diff or PR writeup, module or architecture map, design system or component sheet, prototype, animation tuning, clickable flow, slide deck, status report, incident timeline, post-mortem, research explainer, glossary, comparison table, flowchart, illustration set, custom editor, triage board, feature-flag toggler, prompt tuner, or any deliverable they'll skim, scan, point at, or hand off — even when they don't say "HTML" or "artifact". Skip for chat answers, quick replies, code snippets to paste into an editor, Word docs, .pptx, spreadsheets, or anything that must round-trip to a non-HTML format.

By h00mankind schedule Updated 5/15/2026