mcpField
H
html-ppt-product-launch

html-ppt-product-launch

github.com/nexu-ioDocuments104.6k181 installsUpdated today
Repository

About html-ppt-product-launch

A focused entry point to the `html-ppt` skill’s `product-launch` full-deck template for creating product launch presentations. It explains how to include shared assets and preserve the template’s structure and speaker-note conventions.

Key features

  1. 01Product launch full-deck template
  2. 02Copy or inline shared assets
  3. 03Theme replacement
  4. 04Preserve template structure classes
  5. 05Speaker-note guidance

Use cases

  1. 01Create a product launch presentation
  2. 02Move the template into a project
  3. 03Change a presentation’s theme

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nexu-io/open-design --skill html-ppt-product-launch

After installing, type/html-ppt-product-launchin Claude Code to confirm it loaded.

Bundled filesexample.html

Details

From the project README

HTML PPT · Product Launch

A focused entry point into the html-ppt 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 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 — 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 <link>/<script> tags in index.html from ../../../assets/... to the matching project-local paths (assets/fonts.css, assets/base.css, assets/animations/animations.css, assets/runtime.js).
    • Recipe B — inline: read the same four files and replace each <link rel="stylesheet" href="../../../assets/..."> with a <style>...</style> containing the file's contents, and the <script src="../../../assets/runtime.js"> with a <script>...</script> 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 <link id="theme-link"> 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 <aside class="notes"> or <div class="notes"> — never as visible text on the slide.

Attribution

Visual system, layouts, themes and the runtime keyboard model come from the upstream MIT-licensed lewislulu/html-ppt-skill. The LICENSE file ships at skills/html-ppt/LICENSE; please keep it in place when redistributing.

Comments

Markdown supported