HTMLPPT.skill

Turn an established Hero or frontend project into a coherent, runnable HTML slide deck. Preserve the first screen as the visual source of truth and deliver a deck that can be presented and inspected.

Route

• Use when the user wants multiple presentation pages, a slide deck, or a presentation-style HTML experience.
• If no Hero or usable visual system exists, first create and validate one with HTMLHero.skill, then extend it.
• A true .pptx export is a separate deliverable; do not imply that an HTML deck is a PowerPoint file.

Workflow

1. Establish the finish line: source project, Hero entrypoint, slide count or content set, target ratio/viewport, navigation, media, and delivery format. Inspect only relevant files, AGENTS.md, package.json, lockfile, entrypoints, and assets.
2. Resolve a compact deck contract. Read references/deck-contract.md when page data, navigation, or delivery decisions need to be made. Missing final copy becomes a labeled placeholder; do not invent claims or metrics.
3. Apply constraints in this order: user request, existing Hero/design system, project conventions, then skill defaults. Proceed on reversible assumptions when the user has requested implementation. Ask only for a material ambiguity or an external/irreversible action, unless the user explicitly requested an alignment gate.
4. Implement in the existing stack. Reuse the Hero’s tokens, components, typography, media treatment, and motion language; add shared components only when they reduce real repetition. Keep slide content concise enough to present and keep unrelated dirty work intact.
5. Provide presentation behavior appropriate to the request: semantic slide sections, visible focus, keyboard navigation and hash/deep links when navigation is requested, responsive fallback, and reduced-motion behavior. Do not add decorative animation that competes with the content.
6. Read references/validation.md, then build, preview, inspect every slide at the target ratio, and fix issues before delivery.

Completion and delivery

A task is complete when every requested slide renders, the Hero-derived visual system remains coherent, the requested navigation works, and build/preview plus target-viewport inspection have passed or have concrete blockers documented. Continue through fixes instead of stopping after a first draft for routine review.

Report changed files, actual commands and results, preview URL or entrypoint, slide/interaction checks, assumptions and fallbacks, and any known blocker. Create a zip or convert to .pptx only when requested, and clearly label the artifact type.