htmlizelisted

Technical explanation and HTML artifact protocol. Decides whether a deliverable beats markdown, models the reader's questions, chooses a single page or multi-page briefing site, builds it against a craft baseline, and reviews existing artifacts. Fires on three branches: an explicit ask for an HTML, visual, interactive, or site-level deliverable; a plan, report, system explainer, comparison, deck, or diagram whose structure is lost in linear markdown; and improving an HTML deliverable that looks generic, fragmented, or hard to navigate. Production frontend is kiln's territory; a growing knowledge base is wiki-it's; hand-maintained project docs should remain markdown.
lroolle/skills · ★ 0 · AI & Automation · score 65

Install: claude install-skill lroolle/skills

# htmlize The name is the invocation, not the product. Keep `htmlize` because it is discoverable and existing callers know it; do not describe the result as "an HTML." The product is an **artifact** when one page answers one job, and a **technical briefing site** when several reader questions must cohere without being forced into one scroll. HTML is the material. Explanation is the work. Two modes: - **Create:** turn task evidence and technical reasoning into a reading experience. - **Review:** diagnose an existing artifact or briefing site against the same contracts. The protocol is Gate -> Frame -> Map -> Build -> Check. Review mode runs Check first, then repairs only the failed contracts. ## 1 -- Gate Ask two questions in order: does this deserve HTML, and if so, does it deserve a site? Stay in markdown when any of these hold: | Signal | Why markdown wins | |---|---| | The answer fits in one screen | A page would be ceremony | | The deliverable is code or shell instructions | Fences are already the right interface | | It belongs in git and humans will edit the prose | Markdown diffs and edits cleanly | | It is read once, top to bottom | Navigation would add no leverage | | The structure is headings plus paragraphs | HTML would only impersonate layout | Use HTML when spatial comparison, diagrams, navigation, direct manipulation, or a purpose-built view carries meaning prose would bury. Length is supporting evidence, never the reason by itself. Then choose the