Produce a single self-contained .html file that presents content far more expressively than Markdown. Markdown is clean but flat - it cannot draw a diagram, lay out a card grid, annotate a diff in the margin, color-code a callout, run as a navigable slide deck, offer a download button for a result file, or let the reader tick four boxes and hand the answer back. This skill outputs HTML that can.

The motivating ritual: after a long, intensive run - a research loop that tried 200 ideas, a multi-hour build, a deep refactor - ask for an HTML deck of what worked, what did not, and what to do next. Page through it with a coffee: clear slides, honest reflection, and buttons to download the best artifacts. HTML beats Markdown for exactly this.

Three output profiles cover almost everything:

Deck - fullscreen slides with keyboard / click / swipe navigation, a progress bar, and a counter. Use for a recap of completed work, a highlights showcase, a pitch, a walkthrough, anything meant to be presented one beat at a time.
Document - one long scrolling page with sections, tables, and inline diagrams. Use for architecture write-ups, reports, specs, annotated diffs, explainers, references, anything meant to be read and scanned.
Interactive - a page the reader manipulates and then hands back: pick options, drag items into columns, drag sliders, edit a prompt - then click Copy as markdown and paste the result to you. Use whenever the next step is the reader's decision rather than their understanding.

The third profile is the one people forget. A deck ends the conversation; an interactive page closes the loop, and what it produces is a better prompt than the reader would have typed. Reach for it when you are about to ask "which of these do you want?" - build the sheet instead of asking in prose.

When the user does not specify, infer the profile from intent (see references/content-guide.md): "deck / presentation / slides / recap / showcase / highlights" lean deck; "doc / report / reference / overview / architecture / spec" lean document; "pick / choose / prioritize / triage / tune / tweak / which of these" lean interactive. If genuinely ambiguous, ask once.

rich-html

Workflow