What problem does it solve?
Converts structured storyboard and design specifications into final per-page HTML slides so designers and content owners do not need to hand-code layouts, enforce style rules, or manually place assets for each slide. It ensures consistent canvas size, strict style-spec fidelity, asset consumption, and verifiable markup for review and export.
Core Features & Use Cases
- Per-page HTML export: produces pages/page_01.html … pages/page_XX.html, one file per slide, suitable for downstream export or publishing.
- Strict layout and safety rules: enforces fixed 1280×720 canvas, no scrolling, footer safety zone for page numbers, and required DOM structure (.wrapper, #bg, #ct, #footer).
- Style and asset fidelity: consumes style-spec.json, storyboard.json, and optional asset-plan.json to faithfully render background motifs, foreground motifs, inline SVGs, and prioritized local assets while honoring payload_budget constraints.
- Reviewable outputs: embeds data-display-id and data-atom-ids on visible items for automated review and partial re-rendering support.
- Use case: automated production of a corporate deck where each storyboard page must be rendered exactly to spec and reviewed for asset and data completeness.
Quick Start
Use the ppt-page-html skill to render all storyboard.json pages into pages/ as 1280×720 HTML files that follow style-spec.json and asset-plan.json.
