simple-deck — Claude Code skill: what it does, how to install
simple-deck builds a slide deck as one swipeable HTML file from a seed template and 8 layouts. Fits when you want slides in your design system's colors and fonts.
Apache-2.0 242 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill simple-deck -a claude-codeWhat simple-deck does
simple-deck produces a presentation as a single index.html that swipes horizontally. The agent starts from assets/template.html, which holds the tokens and a ready navigation script, then swaps the six :root variables for tokens from the active DESIGN.md. Slides come from references/layouts.md, which has 8 layouts.
Before any markup, the agent picks a slide count and shows you the light/dark sequence. Six slides is the default; a 15-minute pitch gets 8–10 and a longer talk 12–18. Every slide carries a theme class (light, dark, hero light or hero dark) and a data-screen-label. Three same-theme slides in a row are not allowed, and grep 'class="slide' index.html is how the agent checks it.
The navigation script stays untouched because it handles iframe quirks. scrollIntoView() breaks inside an iframe, so slides never call it. The sample prompt in the skill asks for a strategy deck for a leadership team and begins by asking about audience and decision target.
What it helps with
- build a horizontal-swipe HTML deck in a single
index.html - map design-system tokens onto the six
:rootvariables - plan the light and dark slide rhythm before writing markup
- fill one of 8 ready layouts with real copy
- check slide themes with
grepand a checklist
Example prompts for the agent
- Use the simple-deck skill to build an 8-slide leadership deck on our operating review
- With simple-deck, make an HTML deck from our
DESIGN.mdtokens and show me the theme rhythm first - Run simple-deck for a 15-minute pitch and check the slide themes against the checklist
How to install simple-deck
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill simple-deck -a claude-code2Manually: put the files in place
~/.claude/skills/simple-deck/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/simple-deck/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill simple-deck -a codex2Manually: put the files in place
.agents/skills/simple-deck/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill simple-deck -a cursor2Manually: put the files in place
.cursor/skills/simple-deck/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/simple-deck/SKILL.md2Manually: put the files in place
.github/skills/simple-deck/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill simple-deck -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/simple-deckManually: put the files in place
.devin/skills/simple-deck/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill simple-deck -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about simple-deck
How do I install simple-deck in Claude Code?
Run npx skills add nexu-io/open-design --skill simple-deck -a claude-code. The skill file lands at ~/.claude/skills/simple-deck/SKILL.md.
What does simple-deck do?
It builds a presentation as one index.html with horizontal swiping, using a seed template and 8 slide layouts. Your design system's tokens are filled in for you.
Does simple-deck need a design system?
Yes. It reads the active DESIGN.md and copies its tokens into the six :root variables, so have one in place before you start.
Source text
SKILL.md · Apache-2.0
---
name: simple-deck
en_name: "Write an Operating Review like a Disciplined COO"
zh_name: "像克制的 COO 一样写经营复盘"
description: |
OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.
en_description: |
OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.
zh_description: |
像克制的 COO 一样写经营复盘——一份可商业交付的企业战略 Deck,围绕真实主题、证据链与决策目标组织。
tags:
- "corporate-strategy"
- "board-pre-read-deck"
- "strategy"
- "board"
- "business-review"
- "decision-deck"
- "commercial-slide-agent"
- "simple-deck"
triggers:
- "board-pre-read-deck"
- "corporate-strategy"
- "Write an Operating Review like a Disciplined COO"
- "像克制的 COO 一样写经营复盘"
- "board"
- "strategy"
- "business-review"
- "html deck"
- "html slides"
od:
mode: deck
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
category: "corporate-strategy"
scenario: "strategy"
example_prompt: "Create \"Write an Operating Review like a Disciplined COO\" as a decision-grade Corporate strategy deck in this template's own visual system. Subject: OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Audience: leadership team. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: would a board member know what to approve and why before page five."
---
# Simple Deck Skill
Produce a single-file horizontal-swipe HTML deck using the seed and layout library.
## Resource map
```
simple-deck/
├── SKILL.md ← you're reading this
├── assets/
│ └── template.html ← seed: tokens + slide primitives + proven nav script (READ FIRST)
└── references/
├── layouts.md ← 8 paste-ready slide layouts + theme-rhythm rules
└── checklist.md ← P0/P1/P2 self-review (rhythm spot-check at bottom)
```
## Workflow
### Step 0 — Pre-flight
1. **Read `assets/template.html`** end-to-end through the `<style>` block AND the `<script>` block. The script solves five iframe-specific bugs (real scroller detection, dual capture-phase listeners, auto-focus, no `scrollIntoView`, position persistence) — do not rewrite it.
2. **Read `references/layouts.md`** so you know the 8 layouts. Pay special attention to the "Theme rhythm" section — it's the rule that prevents the deck from feeling sleepy.
3. **Read the active DESIGN.md** — map its tokens to the six `:root` variables in the seed.
### Step 1 — Copy the seed
Copy `assets/template.html` to the project root as `index.html`. Replace the six `:root` variables with the active design system's tokens. Replace the page `<title>`.
### Step 2 — Decide slide count + theme rhythm BEFORE writing any slide
Default: 6 slides unless the brief says otherwise.
| Audience / format | Slides |
|---|---|
| Product overview / lightning talk (5–10 min) | 6 |
| Pitch deck (15 min) | 8–10 |
| Investor update / longer talk (20–30 min) | 12–18 |
Then write out the rhythm before any HTML — for example, 8 slides:
```
01 hero light center Cover
02 light Problem
03 hero dark center Big stat
04 light Three points
05 dark Pipeline
06 hero light center Quote
07 light Before / after
08 hero dark center Ask
```
A healthy sequence has:
- No 3+ same theme in a row
- ≥ 1 `hero dark` AND ≥ 1 `hero light` (for 8+ slides)
- Alternating breath every 3–4 slides
Show this rhythm sketch to the user *before* writing slide HTML — they can redirect cheaply.
### Step 3 — Paste and fill
For each planned slide, copy the matching `<section>` from `layouts.md` into the body. Replace bracketed text with real, specific copy. **No filler / no lorem.** If a slide feels empty, the layout is wrong — pick a different one.
Tag each slide with `data-screen-label="01 Cover"`, `"02 Problem"`, etc., in the order you wrote them. (The seed's first three slides already do this — extend the pattern.)
### Step 4 — Self-check
Run through `references/checklist.md`. The "Theme rhythm spot-check" at the end is non-negotiable:
```bash
grep 'class="slide' index.html
```
Read the resulting class list. If you see `light × 4 in a row`, swap one to `dark`. If no `hero dark` exists in an 8+ slide deck, promote one big-stat or closing slide.
### Step 5 — Write the project file
Write the completed deck HTML to `index.html`.
Then send one short ordinary assistant summary naming `index.html` and describing the deck. Do not output the full HTML source in chat and do not emit a source-code `<artifact>` block.
## Hard rules
- **Theme class on every slide** (`light` | `dark` | `hero light` | `hero dark`). Bare `class="slide"` = regression.
- **No 3+ same theme in a row.**
- **Display = serif via `var(--font-display)`.** `.h-hero` / `.h-xl` / `.h-md` already enforce.
- **One accent per slide, used at most twice.**
- **Don't rewrite the nav script.** It's proven.
- **No `scrollIntoView()`.** Breaks iframe.
- **`data-screen-label` on every slide.**
© nexu-io · Apache-2.0 · nexu-io/open-design