Skip to content
Skills Library
Documents & office · Building & coding

web-slides

/web-slides

Build stunning, research-backed web slide decks (React + Vite + Motion, 1920x1080) with cited figures, full-sentence takeaway titles, WCAG contrast checks, Playwright screenshots, automated self-review and PDF/PNG export. Use when the user asks for a presentation, slide deck, keynote, pitch, briefing or "slides" and wants it fancy, animated or web-based, or needs a PDF of a polished deck. Not for editing an existing .pptx file.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
80
Scripts
45
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 45 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/new-deck.mjs, template/scripts/check-tokens.mjs, template/scripts/critique.mjs, template/scripts/export-pdf.mjs, template/scripts/lib.mjs, template/scripts/lint-in-page.js, template/scripts/live.mjs, template/scripts/review.mjs

What it does and when to use it

Build stunning, research-backed web slide decks (React + Vite + Motion, 1920x1080) with cited figures, full-sentence takeaway titles, WCAG contrast checks, Playwright screenshots, automated self-review and PDF/PNG export. Use when the user asks for a presentation, slide deck, keynote, pitch, briefing or "slides" and wants it fancy, animated or web-based, or needs a PDF of a polished deck. Not for editing an existing .pptx file.

Triggers from the description

slides
Original author description

Build stunning, research-backed web slide decks (React + Vite + Motion, 1920x1080) with cited figures, full-sentence takeaway titles, WCAG contrast checks, Playwright screenshots, automated self-review and PDF/PNG export. Use when the user asks for a presentation, slide deck, keynote, pitch, briefing or "slides" and wants it fancy, animated or web-based, or needs a PDF of a polished deck. Not for editing an existing .pptx file.

How it works

  1. Non-negotiable standard
  2. Workflow
  3. Engine at a glance
  4. User media (agent)
  5. Style import (agent)
  6. Design spec + live mode
  7. Don'ts
Original SKILL.md headings · 89 lines, 1,960 words
SKILL.md preview
---
name: web-slides
description: Build stunning, research-backed web slide decks (React + Vite + Motion, 1920x1080) with cited figures, full-sentence takeaway titles, WCAG contrast checks, Playwright screenshots, automated self-review and PDF/PNG export. Use when the user asks for a presentation, slide deck, keynote, pitch, briefing or "slides" and wants it fancy, animated or web-based, or needs a PDF of a polished deck. Not for editing an existing .pptx file.
license: MIT
compatibility: Needs Node.js 20+ and npm, network access for npm install, and a Chromium for Playwright (npx playwright install chromium, or CHROME_PATH).
metadata:
  version: "0.8.0"
  companion: "style-library, slide-reviewer"
  stack: "react 19, vite 8, motion 14, playwright, mermaid, shiki, lucide-react, echarts 6 (lazy)"
---

# Web Slides

Make keynote-grade decks as a small React app, then prove they are good with screenshots and an automated review before handing them over.

Paths below are relative to this skill directory. Read files in `references/` when a step tells you to.

## Non-negotiable standard

1. **Research first. Only sourced figures.** Every number, chart, quote and factual claim comes from a source you opened in this session. Each slide lists its sources in the footer, and each figure uses `cite="id"`. If you do not have a source, cut the figure or ask the user. Never invent numbers, quotes, logos or customer names. A figure that is only an example must use `illustrative` (it shows an "Illustrative" label).
2. **Every slide title is a full-sentence takeaway.** For example, "Ticket triage time fell 48% after the pilot." is a takeaway; "Results" is not.
3. **Technical topics need four slide types:** architecture, results, governance (risk, security, controls, ownership) and lessons.
4. **WCAG 2.2 AA contrast.** Normal text needs 4.5:1 and large text needs 3:1. `npm run check:tokens` and `npm run review` both enforce this.
5. **Consistent icons.** Use only lucide-react through `<Icon>`, `<Card icon>` or `<IconList>`. Use one stroke weight and the fixed sizes. No emoji and no mixed icon sets. **User-provided logos/photos/screenshots** go through `<Figure>` — read `references/media-guide.md` and copy files into `public/media/`.
6. **No template leftovers.** Delete every example slide you do not use. Do not leave lorem, TODO, TBD, `{{ }}`, example sources or "Illustrative" figures in a final deck unless the user agreed.
7. **Theme by tokens only.** Every color, font and size lives in `src/theme/tokens.css`. Built-in themes: `midnight`, `aurora`, `paper`, plus inspiration presets `tech-dark`, `bento-minimal`, `navy-pitch` (see `docs/template-inspiration.md`). A user brand goes in `src/theme/brand.css` as `[data-theme="brand"]`. Never hard-code hex values in slides.
8. **Prefer built-in presets; borrow style, not assets.** Default to a built-in theme (or an inspiration preset) instead of re-scraping SlidesCarnival / Slidesgo each run. Use `npm run style:url` / `style:images` / `style:svg` **only when the user supplies a new brand** (their site, images or SVGs). Never copy third-party logos, photos, fonts, or vendor PPTX/GS packs into the repo. Swap fonts like SF Pro for Inter. Canva elements need the user's confirmation of rights. See `references/style-import.md` and `docs/template-inspiration.md`.
9. **Reuse named style packs via `style-library`.** When the user likes a deck/theme/component look (title hero, KPI strip, timeline, …) and wants it again later, use the sibling skill `skills/style-library/` (`save` / `list` / `apply` / `update`). Packs hold original CSS/TSX snapshots + recipes — not third-party PPTX. After a successful `style:url`/`images`/`svg` import, offer to `save` the brand as a pack.

## Workflow

Follow these steps in order, and stop at the approval gate. The full details are in `references/workflow.md`.

1. **Brief.** Get the audience, goal, length (minutes or slide count), the decision or ask, and the deadline. Also ask whether a brand palette exists, a saved **style-library** pack, or a website/images/SVGs to match (steps 5–6). If there is none, use a built-in theme (`midnight`, `aurora`, `paper`) or an inspiration preset (`tech-dark`, `bento-minimal`, `navy-pitch`) — do **not** scrape free template sites by default.
2. **Research.** Collect sources into a working notes file with URLs and the exact figures and quotes. Prefer primary sources such as official docs, papers, filings and the user's own data.
3. **Design spec, then approval.** From the user's raw notes (no layout required), write `content/deck.spec.yaml` — slide order, takeaway titles, types from `references/slide-catalog.md`, layout recipes from `references/layout-guide.md`, components (Stat/BarChart/EChart/Mermaid/LayeredArchitecture/FlowSteps/Sequence/C4Container/Figure/Code/Timeline/…), text, media paths, chart data, sources, speaker notes. Schema: `references/deck-spec.md`. **Show that file to the user, let them edit it, and wait for approval** (`approved: true` only after they say yes) before generating production React slides, unless they explicitly said to skip approval. A thin `outline.md` brainstorm is optional; `content/deck.outline.md` remains an optional light stub for `npm run live`.
4. **Scaffold.** Run `node scripts/new-deck.mjs <dir> --title "<takeaway title>" [--theme midnight|aurora|paper|tech-dark|bento-minimal|navy-pitch]`, then `cd <dir> && npm install && npx playwright install chromium`. Use `--keep-examples` only if you want the 17 example slides as a reference; delete them afterwards.
5. **Style import (only when the user supplies a new brand).** Prefer built-in / inspiration presets from step 1. If they give their own website URL, brand images or SVG artwork, run one of these in the deck:
   - `npm run style:url -- <url>`
   - `npm run style:images -- <dir>`
   - `npm run style:svg -- <dir>`

   Add `--apply` to switch the deck to `theme: "brand"`. Each command writes `style-import/style-spec.json` and `src/theme/brand.css`, auto-fixes failing contrast while keeping hue, and runs `check:tokens`. Read the summary, sanity-check it against the captures, install any non-bundled font it names, and tell the user which brand colors were adjusted and which fonts were swapped. SVGs land classified in `public/media/svg/` (background, frame, decorative, icon). Full workflow, mapping rules, font table and licensing: `references/style-import.md`. Preview any theme with `?theme=brand` or `npm run review -- --theme brand`.
6. **Style library (reuse).** If the brief names a pack, or you saved one earlier: from the repo root run `npm run style-lib -- apply --id <pack-id> --deck <dir>`. Apply **wires the build**: `brand.css`, `theme: "brand"`, `content/style-pack.json`, patched `deck.spec.yaml` (pattern/layout/title-hero fields), matching slide TSX, and `src/slides/generated/from-pack.ts` (recipes also land in `style-import/pack-<id>/`). Then `npm run spec`. When the user likes the current look, `save` / `update` a pack. Sibling: `skills/style-library/SKILL.md`.
7. **Build the slides from the approved spec.** Run `npm run spec` to validate and emit stubs for `status: stub` into `src/slides/generated/from-spec.tsx`. Promote each stub into `src/slides/NN-id.tsx`, set `status: locked` in the YAML, and register the polished module in `src/slides/index.ts` (see promote/merge in `references/deck-spec.md` — regenerating must not wipe locked slides). Add sources to `src/slides/sources.ts`. Copy patterns from `template/src/slides/*` and follow `references/design-guide.md` and `references/layout-guide.md`. For architecture or flow visuals, open `references/diagram-guide.md`. For data charts beyond a simple bar comparison, open `references/chart-guide.md`. **When the user provides images, logos, screenshots or says "use this asset", follow `references/media-guide.md` end-to-end.** Use **`npm run dev`** or **`npm run live`** while polishing — see Live mode below.
8. **Screenshots and review.** Run `npm run review`. It builds the deck, screenshots every slide in its final state into `review/`, writes `review/contact-sheet.png` and `review/report.md`, and exits non-zero on errors.
9. **Critique (slide-reviewer).** Run `npm run critique` (sibling skill `skills/slide-reviewer/`). It writes `review/critique.md` from the lint report. Open the contact sheet and every PNG; add **Visual findings** (overlap, density, weak titles, safe margins, title-hero issues). Show the critique to the user. **Do not auto-rewrite** slides unless they ask you to fix specific findings.
10. **Self-review + fixes.** Go through `references/review-checklist.md` and any user-approved critique items. Fix, then re-run `npm run review` and `npm run critique` until lint has 0 errors and the critique is accepted (or they skip). Use `npm run review -- --steps` for click-steps.
11. **Export.** Run `npm run export:pdf`, which writes `export/deck.pdf` with vector, selectable text. If blur or glow effects print wrong, also run `npm run export:pdf -- --raster` for `export/deck-raster.pdf`. `npm run export:png` writes PNGs to `export/png/`. `npm run verify` runs the token check, typecheck, build, review and PDF export in one go.
12. **Hand-off.** Give the user the PDF, the contact sheet, how to present (`npm run dev`, or open `dist/` from any static host), the list of sources, and anything you could not source.

## Engine at a glance

- The stage is 1920×1080 and scaled to fit. Body layouts: `.layout-stack`, `.layout-kpi`, `.layout-compare`, `.layout-media`, `.layout-hero`, `.layout-bento`, `.layout-section`, `.layout-timeline-strip` (+ `.grid-2/3/4`, `.row`) — see `references/layout-guide.md`. Present mode keys: ←/→, Space, PgUp/PgDn, Home/End, **N** notes, **O** overview, **F** fullscreen (keys with Ctrl/Cmd/Alt are left to the browser). URLs look like `#/slide/step`; editing the hash jumps there, and a step past the slide's last is clamped.
- `?static&slide=N&step=final` renders one slide for screenshots, and `?print` renders all slides for PDF. In both, motion is off and every step is shown.
- Click steps: set `steps: n` on the slide, then use `<Appear at={k}>`, `<Stagger stepwise>`, `<IconList stepwise>`, `<Timeline>`, or `<Code focus={[...]}>`.
- Components (`src/deck/components.tsx`): `SlideFrame`, `Appear`, `Stagger`, `Card`, `Icon`, `Pill`, `Stat`, `BarChart`, `EChart`, `Figure`, `Mermaid`, `Code`, `Timeline`, `Quote`, `IconList`, `Gradient`, `Cite`.
- Charts: `BarChart` for 3–7 bar comparisons; `EChart` (lazy-loaded ECharts, SVG, themed from tokens) for trends, stacked part-to-whole, distributions, scatter, sankey and heatmaps. **Read `references/chart-guide.md`** before charting: pick the type from the story, accent the series the title names (`highlight`), bars from zero, no pie, 3D or dual axes.
- Diagrams (`src/deck/diagrams.tsx`, re-exported): `LayeredArchitecture`, `FlowSteps`, `Sequence`, `C4Container`, `DiagramLegend`. **Read `references/diagram-guide.md`** before drawing — Mermaid for ≤8-node flows; React+CSS for swimlanes, C4 and sequences. Prop tables are in `references/slide-catalog.md`.
- Motion follows the viewer's `prefers-reduced-motion` setting through `MotionConfig reducedMotion="user"`.

## User media (agent)

When the user drops a file or says "use this logo / screenshot / image", **you** insert it — do not only describe how:

1. Copy the file to `public/media/<kebab-name>.<ext>` in the deck.
2. Add `<Figure src="/media/…" alt="…" cite="…" />` (or `illustrative`) on the slide.
3. Run `npm run review` and confirm the screenshot shows the asset.

Full rules: `references/media-guide.md`. Example: `template/src/slides/16-media-figure.tsx`.

## Style import (agent)

**Prefer built-in themes** (`midnight` / `aurora` / `paper` / `tech-dark` / `bento-minimal` / `navy-pitch`) before scraping. Only when the user says "make it look like *our* site", "use our brand images" or hands you SVGs, **you** run the import. Don't hand-pick hex values, and don't re-fetch SlidesCarnival/Slidesgo packs for a look we already baked in:

| Input | Command | Output |
|---|---|---|
| URL | `npm run style:url -- https://…` | spec, reference captures (gitignored), `brand.css` with colors, fonts and layout tokens |
| Images | `npm run style:images -- ./refs` | k-means palette, mood, `brand.css` (`--copy` puts owned images in `public/media/imported/`) |
| SVGs | `npm run style:svg -- ./art` | palette, `brand.css`, and normalized `public/media/svg/<kind>-*.svg` (icons use `currentColor`) |

Then run `npm run review`, look at the contact sheet, and report the palette, the contrast fixes and the font swaps. Use imported SVG backgrounds and decorations via `<Figure decorative frame={false}>`.

## Design spec + live mode

1. **`content/deck.spec.yaml`** — editable middle layer and **approval gate** (`references/deck-spec.md`). User edits design; agent sets `approved: true` only after explicit approval, then `npm run spec` (validate + stub generate). `status: locked` slides are never overwritten.
2. **`npm run dev`** — Vite present mode at http://127.0.0.1:5173 with HMR. Edit any `src/slides/*.tsx`, `sources.ts`, theme CSS, or diagram component; the browser updates immediately. Keys: ←/→, Space, **N** notes, **O** overview, **F** fullscreen.
3. **`npm run live`** — same as dev, plus watches the optional light `content/deck.outline.md` → `from-outline.tsx`. Prefer the YAML spec; sync a light outline with `npm run spec -- --sync-outline`. Uncomment `specSlides` / `outlineSlides` in `index.ts` only while iterating.

Do not treat stubs as final deck quality. Diagrams, motion and tight layout stay in hand-written (locked) React.

## Don'ts

- Don't put more than about 40 words of body text on a slide; move detail to the `notes`.
- Don't use text smaller than 18px on the stage (the lint enforces this, including diagram text). Don't use more than 6 cards or 5 bullets. Don't put more than 8 nodes in Mermaid; for denser architecture use `LayeredArchitecture` / `C4Container` / `Sequence` (see `diagram-guide.md`), and still split if a swimlane exceeds 6 layers or 5 cells.
- Don't use `position: absolute` for everyday content (SlideFrame chrome, `.bg`, and title `.title-backdrop` / `.title-scrim` only). Title openers: left hero + optional full-bleed `backdrop` (not centered). Prefer Grid/Flex per `references/layout-guide.md`. Don't use raw hex colors (in slides or in an `EChart` option), hotlinked images you don't have rights to, invented logos, stock "AI brain" art, or pie or 3D charts. Put user media in `public/media/` via `<Figure>`.
- Don't ship `style-import/captures/*` or any third-party screenshot, logo or font file. They are reference only.
- Don't skip the design-spec approval gate (`content/deck.spec.yaml`) or the screenshot review. Don't regenerate over `status: locked` slides.
Files in this package (80)
  • SKILL.md 15 KB
  • fixtures/style-import/README.md 1 KB
  • fixtures/style-import/images/moodboard-night.png 14 KB
  • fixtures/style-import/images/moodboard-paper.png 2 KB
  • fixtures/style-import/images/moodboard-tide.png 1 KB
  • fixtures/style-import/svg/corner-frame.svg 1 KB
  • fixtures/style-import/svg/orbit-decor.svg 1 KB
  • fixtures/style-import/svg/spark-icon.svg 1 KB
  • fixtures/style-import/svg/wave-background.svg 1 KB
  • references/chart-guide.md 6 KB
  • references/deck-spec.md 11 KB
  • references/design-guide.md 7 KB
  • references/diagram-guide.md 7 KB
  • references/layout-guide.md 9 KB
  • references/media-guide.md 6 KB
  • references/review-checklist.md 6 KB
  • references/slide-catalog.md 8 KB
  • references/style-import.md 13 KB
  • references/workflow.md 6 KB
  • scripts/new-deck.mjs 6 KB
  • template/.gitignore 1 KB
  • template/index.html 1 KB
  • template/package-lock.json 114 KB
  • template/package.json 1 KB
  • template/tsconfig.json 1 KB
  • template/vite.config.ts 1 KB
  • template/content/deck.outline.md 1 KB
  • template/content/deck.spec.yaml 6 KB
  • template/public/media/README.md 1 KB
  • template/public/media/illustrative-mesh.svg 1 KB
  • template/public/media/title-hero-photo-placeholder.jpg 85 KB
  • template/public/media/title-hero-plate.svg 1 KB
  • template/scripts/check-tokens.mjs 2 KB
  • template/scripts/critique.mjs 7 KB
  • template/scripts/export-pdf.mjs 2 KB
  • template/scripts/lib.mjs 2 KB
  • template/scripts/lint-in-page.js 16 KB
  • template/scripts/live.mjs 1 KB
  • template/scripts/review.mjs 8 KB
  • template/scripts/spec.mjs 19 KB
  • template/scripts/watch-outline.mjs 4 KB
  • template/scripts/style/images.mjs 4 KB
  • template/scripts/style/lib.mjs 22 KB
  • template/scripts/style/svg.mjs 8 KB
  • template/scripts/style/url.mjs 10 KB
  • template/src/main.tsx 1 KB
  • template/src/deck/Deck.tsx 8 KB
  • template/src/deck/components.tsx 20 KB
  • template/src/deck/context.tsx 2 KB
  • template/src/deck/deck.css 30 KB
  • template/src/deck/diagrams.tsx 13 KB
  • template/src/deck/echart.tsx 9 KB
  • template/src/deck/echarts-lib.ts 1 KB
  • template/src/deck/types.ts 1 KB
  • template/src/slides/01-title.tsx 1 KB
  • template/src/slides/02-agenda.tsx 1 KB
  • template/src/slides/03-big-number.tsx 1 KB
  • template/src/slides/04-comparison.tsx 2 KB
  • template/src/slides/05-architecture.tsx 1 KB
  • template/src/slides/06-timeline.tsx 1 KB
  • template/src/slides/07-code.tsx 1 KB
  • template/src/slides/08-results.tsx 1 KB
  • template/src/slides/09-quote.tsx 1 KB
  • template/src/slides/10-governance.tsx 1 KB
  • template/src/slides/11-lessons.tsx 1 KB
  • template/src/slides/12-closing.tsx 1 KB
  • template/src/slides/13-layered-platform.tsx 2 KB
  • template/src/slides/14-c4-context.tsx 2 KB
  • template/src/slides/15-chat-sequence.tsx 2 KB
  • template/src/slides/16-media-figure.tsx 2 KB
  • template/src/slides/17-trend-chart.tsx 2 KB
  • template/src/slides/index.ts 1 KB
  • template/src/slides/measured.ts 1 KB
  • template/src/slides/sources.ts 2 KB
  • template/src/slides/generated/.gitkeep 1 KB
  • template/src/slides/generated/from-outline.tsx 3 KB
  • template/src/slides/generated/from-spec.tsx 1 KB
  • template/src/slides/generated/spec-manifest.json 2 KB
  • template/src/theme/brand.css 1 KB
  • template/src/theme/tokens.css 8 KB

Versions

The database has no other skills named web-slides.

Database snapshot: 13.11.2026 · package version 9388349a0ffb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100capcut-slides
    Make presentation slide decks as HTML files that open in any browser, present them with speaker notes, export them to PDF, PNG or PowerPoint (PPTX), and turn a deck into a CapCut video draft with music and captions. Use when the user asks for slides, a deck, a presentation, a…
  • 100ai-slides
    Generate complete presentations with AI — from outline to polished slides. Use when a user asks to create a presentation, build slides, make a pitch deck, generate a slide deck, create a keynote, prepare a talk, build a demo presentation, or produce any slide-based content.
  • 93pptx
    Use this skill any time a presentation file is the primary input or output. Covers: creating new .pptx decks from scratch or from an outline/document (pptxgenjs / python-pptx); editing and restyling an existing .pptx; reading and extracting text/structure from a deck…
  • 100slides
    Create and edit presentation decks as single self-contained HTML files with a live, editable preview and print-to-PDF export. Use when the user wants slides, a deck, or a presentation.
  • 100claude-slides
    Make and revise slide decks in the Slides artifact format (project/deck.json plus one HTML file per slide) as local files, then open them in a local slide editor where the user can present, retype, drag, and export PDF, HTML or PowerPoint. Use when the user asks for an editable…
  • 100presentation-builder
    Build real deck artifacts when the user needs editable slides, not just prose: investor decks, roadmap/QBR decks, launch decks, architecture/demo decks, workshop/training decks, and game pitch or milestone decks. Use when the job is to choose one deck mode, one smallest useful…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.