--- name: html-ppt-product-launch description: Launch keynote deck — dark hero + light content, warm orange→peach accent, feature cards, pricing tiers, CTA. Use when announcing a product, launching a feature, or doing a keynote-style reveal. triggers: - "product launch" - "keynote" - "launch deck" - "feature reveal" - "launch slides" - "发布会" od: mode: deck scenario: marketing featured: 21 upstream: "https://github.com/lewislulu/html-ppt-skill" preview: type: html entry: index.html design_system: requires: false speaker_notes: true animations: true example_prompt: "Make a product-launch keynote deck in HTML using the html-ppt-product-launch full-deck template (dark hero, warm orange accent, feature cards, pricing tiers). Confirm: product name + tagline, the 3 key features, and pricing tiers — then write the deck." --- # HTML PPT · Product Launch A focused entry point into the [`html-ppt`](../html-ppt/SKILL.md) master skill that lands the user directly on the **`product-launch`** full-deck template. ## When this card is picked The Examples gallery wires "Use this prompt" to the example_prompt above. When you accept that prompt, this card is the right pick if the user wants exactly the visual identity of `product-launch` (see the upstream [full-decks catalog](../html-ppt/references/full-decks.md) for screenshots and rationale). ## How to author the deck 1. **Read the master skill first.** All authoring rules live in [`skills/html-ppt/SKILL.md`](../html-ppt/SKILL.md) — content/audience checklist, token rules, layout reuse, presenter mode, the keyboard runtime, and the "never put presenter-only text on the slide" rule. 2. **Start from the matching template folder:** `skills/html-ppt/templates/full-decks/product-launch/` — copy `index.html` and `style.css` into the project, keep the `.tpl-product-launch` body class. 3. **Bring the shared runtime with the template.** The upstream `index.html` links the shared CSS/JS via `../../../assets/...` because it sits three folders deep inside `skills/html-ppt/templates/full-decks/`. Once you copy `index.html` into the project, those parent-relative URLs no longer resolve and `base.css`, `animations.css`, and `runtime.js` will 404 — meaning the deck never activates and slide navigation is dead. Pick one of these two recipes per project: - **Recipe A — copy + rewrite (preferred):** copy `skills/html-ppt/assets/fonts.css`, `skills/html-ppt/assets/base.css`, `skills/html-ppt/assets/animations/animations.css`, and `skills/html-ppt/assets/runtime.js` into a project-local `assets/` (with `assets/animations/animations.css`), then rewrite the four ``/`` containing `runtime.js`. Yields a single self-contained `index.html`. Either way, do not ship the upstream `../../../assets/...` URLs verbatim into a project artifact — they only work in-tree. 4. **Pick a theme.** Default tokens look fine; if the user wants a different feel, swap in any of the 36 themes from `skills/html-ppt/assets/themes/*.css` via `` and let `T` cycle. 5. **Replace demo content, not classes.** The `.tpl-product-launch` scoped CSS only recognises the structural classes shipped in the template — keep them. 6. **Speaker notes go inside `