nexu-io/open-design
Open Design 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.
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/html-ppt-tech-sharing"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
A focused entry point into the html-ppt master skill that lands the user directly on the tech-sharing full-deck template.
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/html-ppt-tech-sharing"The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.
461 source words · 3 usable sections
Design process
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
1. 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. 2. Start from the matching tem…
The Examples gallery wires "Use this prompt" to the exampleprompt 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).
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.
Design checklist
The source section “How to author the deck” has been checked.
The source section “When this card is picked” has been checked.
The source section “Attribution” has been checked.
Choose a different workflow
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailGrounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.
Open source detailUse BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.
A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
A focused entry point into the html-ppt master skill that lands the user directly on the tech-sharing full-deck template.
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "design-templates/html-ppt-tech-sharing". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
A focused entry point into the html-ppt master skill that lands the user directly on the tech-sharing full-deck template.
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).
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.design-templates/html-ppt/templates/full-decks/tech-sharing/ — copy index.html and
style.css into the project, keep the .tpl-tech-sharing body class.index.html links the shared CSS/JS via ../../../assets/... because it
sits three folders deep inside design-templates/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:
design-templates/html-ppt/assets/fonts.css, design-templates/html-ppt/assets/base.css,
design-templates/html-ppt/assets/animations/animations.css, and
design-templates/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).<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.design-templates/html-ppt/assets/themes/*.css
via <link id="theme-link"> and let T cycle..tpl-tech-sharing scoped CSS only
recognises the structural classes shipped in the template — keep them.<aside class="notes"> or <div class="notes"> — never as visible text on the slide.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.