HTML PPT · Tech Sharing
A focused entry point into the html-ppt master skill that lands the user directly on the tech-sharing 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 tech-sharing (see the upstream full-decks catalog for screenshots and rationale).
How to author the deck
- 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.
- Start from the matching template folder:
skills/html-ppt/templates/full-decks/tech-sharing/ — copy index.html and
style.css into the project, keep the .tpl-tech-sharing body class.
- 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.
- 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.
- Replace demo content, not classes. The
.tpl-tech-sharing scoped CSS only
recognises the structural classes shipped in the template — keep them.
- 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.
1---2name: html-ppt-tech-sharing3description: Conference / internal tech-talk deck — GitHub-dark, JetBrains Mono, terminal code blocks, agenda + Q&A pages. Use for engineering presentations, internal sharing sessions, conference talks, and code-heavy walkthroughs.4---5# HTML PPT · Tech Sharing67A focused entry point into the [`html-ppt`](../html-ppt/SKILL.md) master skill that lands the user directly on the **`tech-sharing`** full-deck template.89## When this card is picked1011The 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 `tech-sharing` (see the upstream [full-decks catalog](../html-ppt/references/full-decks.md) for screenshots and rationale).1213## How to author the deck14151. **Read the master skill first.** All authoring rules live in16 [`skills/html-ppt/SKILL.md`](../html-ppt/SKILL.md) — content/audience checklist,17 token rules, layout reuse, presenter mode, the keyboard runtime, and the18 "never put presenter-only text on the slide" rule.192. **Start from the matching template folder:**20 `skills/html-ppt/templates/full-decks/tech-sharing/` — copy `index.html` and21 `style.css` into the project, keep the `.tpl-tech-sharing` body class.223. **Bring the shared runtime with the template.** The upstream23 `index.html` links the shared CSS/JS via `../../../assets/...` because it24 sits three folders deep inside `skills/html-ppt/templates/full-decks/`.25 Once you copy `index.html` into the project, those parent-relative URLs26 no longer resolve and `base.css`, `animations.css`, and `runtime.js`27 will 404 — meaning the deck never activates and slide navigation is28 dead. Pick one of these two recipes per project:29 - **Recipe A — copy + rewrite (preferred):** copy30 `skills/html-ppt/assets/fonts.css`, `skills/html-ppt/assets/base.css`,31 `skills/html-ppt/assets/animations/animations.css`, and32 `skills/html-ppt/assets/runtime.js` into a project-local33 `assets/` (with `assets/animations/animations.css`), then rewrite the34 four `<link>`/`<script>` tags in `index.html` from35 `../../../assets/...` to the matching project-local paths36 (`assets/fonts.css`, `assets/base.css`,37 `assets/animations/animations.css`, `assets/runtime.js`).38 - **Recipe B — inline:** read the same four files and replace each39 `<link rel="stylesheet" href="../../../assets/...">` with a40 `<style>...</style>` containing the file's contents, and the41 `<script src="../../../assets/runtime.js">` with a42 `<script>...</script>` containing `runtime.js`. Yields a single43 self-contained `index.html`.44 Either way, do not ship the upstream `../../../assets/...` URLs45 verbatim into a project artifact — they only work in-tree.464. **Pick a theme.** Default tokens look fine; if the user wants a different47 feel, swap in any of the 36 themes from `skills/html-ppt/assets/themes/*.css`48 via `<link id="theme-link">` and let `T` cycle.495. **Replace demo content, not classes.** The `.tpl-tech-sharing` scoped CSS only50 recognises the structural classes shipped in the template — keep them.516. **Speaker notes go inside `<aside class="notes">` or `<div class="notes">`** — never as visible text on the slide.5253## Attribution5455Visual system, layouts, themes and the runtime keyboard model come from56the upstream MIT-licensed [`lewislulu/html-ppt-skill`](https://github.com/lewislulu/html-ppt-skill). The57LICENSE file ships at `skills/html-ppt/LICENSE`; please keep it in place when58redistributing.
archibate