What problem does it solve? Turning a finished planning spec markdown into a presentable HTML screen is repetitive and error-prone: designers must keep design tokens consistent, map each spec section to a page area, and produce both a Figma-ready static version and a clickable demo. This Skill automates that conversion with a shared template so outputs stay consistent. ## Core Features & Use Cases - Dual output in one run: Generates a static HTML file (input for the Figma conversion step) and an interactive standalone prototype with inline vanilla JS (tabs, steppers, toggles, dynamic lists, validation, live summary) for human review and demos. - Template-driven rendering: Clones the shared template (tokens.css, base.css, template.html) so colors, fonts, and shadows come only from design tokens, with hifi/wire themes and a fixed 1440px canvas. - 1:1 section mapping with integrity checks: Maps each spec section ### N to an .area block (.area-no N) and verifies the counts match across markdown, static, and interactive outputs. - Use Case: After writing a v6 spec md for an alarm settings screen, run this Skill to get html/v6/<screen>.html for Figma conversion plus <screen> (인터랙티브).html for stakeholder review. ## Quick Start Render the spec markdown at md/v6/alarm-settings.md into the shared-template HTML, producing both the static and interactive versions in html/v6.