nexu-io/open-design / plugins/_official/examples/html-ppt-tech-sharing
html-ppt-tech-sharing
VerifiedOpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.
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
design-templates/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:
design-templates/html-ppt/templates/full-decks/tech-sharing/— copyindex.htmlandstyle.cssinto the project, keep the.tpl-tech-sharingbody class. - Bring the shared runtime with the template. The upstream
index.htmllinks the shared CSS/JS via../../../assets/...because it sits three folders deep insidedesign-templates/html-ppt/templates/full-decks/. Once you copyindex.htmlinto the project, those parent-relative URLs no longer resolve andbase.css,animations.css, andruntime.jswill 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
design-templates/html-ppt/assets/fonts.css,design-templates/html-ppt/assets/base.css,design-templates/html-ppt/assets/animations/animations.css, anddesign-templates/html-ppt/assets/runtime.jsinto a project-localassets/(withassets/animations/animations.css), then rewrite the four<link>/<script>tags inindex.htmlfrom../../../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>containingruntime.js. Yields a single self-containedindex.html. Either way, do not ship the upstream../../../assets/...URLs verbatim into a project artifact — they only work in-tree.
- Recipe A — copy + rewrite (preferred): copy
- Pick a theme. Default tokens look fine; if the user wants a different
feel, swap in any of the 36 themes from
design-templates/html-ppt/assets/themes/*.cssvia<link id="theme-link">and letTcycle. - Replace demo content, not classes. The
.tpl-tech-sharingscoped 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 design-templates/html-ppt/LICENSE; please keep it in place when
redistributing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |