html-outputlisted
Install: claude install-skill Rijul1204/rashedul-agentic-engineering
# html-output
Render the current plan, spec, design doc, or conversation context as **one self-contained HTML file** that conveys the information more densely than markdown can — tables, inline SVG diagrams, semantic structure, in-page navigation, mobile-responsive layout, no external runtime dependencies.
*See [README.md](README.md) for the sources that inspired this skill (Thariq Shihipar, Andrej Karpathy) and a before/after demo.*
This skill owns *what* to convert and *where* to put the file. Visual quality (typography, color, motion, layout polish) is delegated to the `frontend-design` skill — if it's installed, treat this skill as composing on top of it. Otherwise default to a clean modern editorial style.
## When to invoke
Fire on any of:
- The user types `/html-output` (optionally followed by a path).
- The user asks to "make this an HTML page", "render as HTML", "export to HTML", "give me a shareable version", "make a web version of this".
- The user uses the Karpathy phrasing: *"structure your response as HTML"*, *"give me this as HTML"*, *"put this in an HTML file"*.
- The user asks for a **slideshow / deck**: *"present this as slides"*, *"make a slide deck"*, *"turn this into a slideshow"*, *"give me this as slides"* — route to the deck mode below.
- The user finishes a long plan / spec / design doc and wants a more readable artifact.
Do **not** fire on:
- Source < 30 lines (ask first — HTML overhead is rarely worth it; a slideshow needs ≥ ~5 logical sectio