web-slides
Skill0 starsChanged 12 days agoMITView on GitHub
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.
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- yiyu-works/skillstheir own version, first seen Oct 20, 2026
- olddonkey/olddonkey-skillstheir own version, first seen Oct 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- olddonkey/olddonkey-skills★ 17same name
- yiyu-works/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- slide-reviewerSkill
- style-librarySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 3 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Consistent icons: Use only lucide-react through <Icon>, <Card icon> or <IconList>.
- Very specific: line 25
No template leftovers: Delete every example slide you do not use.
- Very specific: line 26
Theme by tokens only: Every color, font and size lives in src/theme/tokens.css.
- Very specific: line 32
Follow these steps in order, and stop at the approval gate.
- Very specific: line 37
Scaffold: Run node scripts/new-deck.mjs <dir> --title "<takeaway title>" [--theme …
- Distinctive: line 38
Style import (only when the user supplies a new brand): Prefer built-in / inspiration presets from step 1.
- Very specific: line 46
Screenshots and review: Run npm run review. It builds the deck, screenshots every slide in its final state into review/, writes …
- Very specific: line 49
Export: Run npm run export:pdf, which writes export/deck.pdf with vector, selectable text.
- Distinctive: line 64
When the user drops a file or says "use this logo / screenshot / image", you insert it — do not only describe how:
- Very specific: line 67
Add <Figure src="/media/…" alt="…" cite="…" /> (or illustrative) on the slide.
- Very specific: line 68
Run npm run review and confirm the screenshot shows the asset.
- Distinctive: line 90
Do not treat stubs as final deck quality.
- Very specific: line 94
Don't put more than about 40 words of body text on a slide.
- Very specific: line 97
Don't ship style-import/captures/* or any third-party screenshot, logo or font file.
- Very specific: line 98
Don't skip the design-spec approval gate (content/deck.spec.yaml) or the screenshot review.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- 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 useillustrative(it shows an "Illustrative" label). - Every slide title is a full-sentence takeaway. For example, "Ticket triage time fell 48% after the pilot." is a takeaway; "Results" is not.
- Technical topics need four slide types: architecture, results, governance (risk, security, controls, ownership) and lessons.
- WCAG 2.2 AA contrast. Normal text needs 4.5:1 and large text needs 3:1.
npm run check:tokensandnpm run reviewboth enforce this. - 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>— readreferences/media-guide.mdand copy files intopublic/media/. - 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. - Theme by tokens only. Every color, font and size lives in
src/theme/tokens.css. Built-in themes:midnight,aurora,paper, plus inspiration presetstech-dark,bento-minimal,navy-pitch(seedocs/template-inspiration.md). A user brand goes insrc/theme/brand.cssas[data-theme="brand"]. Never hard-code hex values in slides. - 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:svgonly 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. Seereferences/style-import.mdanddocs/template-inspiration.md. - 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 skillskills/style-library/(save/list/apply/update). Packs hold original CSS/TSX snapshots + recipes — not third-party PPTX. After a successfulstyle:url/images/svgimport, offer tosavethe brand as a pack.
Workflow
Follow these steps in order, and stop at the approval gate. The full details are in references/workflow.md.
- 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. - 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.
- Design spec, then approval. From the user's raw notes (no layout required), write
content/deck.spec.yaml— slide order, takeaway titles, types fromreferences/slide-catalog.md, layout recipes fromreferences/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: trueonly after they say yes) before generating production React slides, unless they explicitly said to skip approval. A thinoutline.mdbrainstorm is optional;content/deck.outline.mdremains an optional light stub fornpm run live. - Scaffold. Run
node scripts/new-deck.mjs <dir> --title "<takeaway title>" [--theme midnight|aurora|paper|tech-dark|bento-minimal|navy-pitch], thencd <dir> && npm install && npx playwright install chromium. Use--keep-examplesonly if you want the 17 example slides as a reference; delete them afterwards. 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
--applyto switch the deck totheme: "brand". Each command writesstyle-import/style-spec.jsonandsrc/theme/brand.css, auto-fixes failing contrast while keeping hue, and runscheck: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 inpublic/media/svg/(background, frame, decorative, icon). Full workflow, mapping rules, font table and licensing:references/style-import.md. Preview any theme with?theme=brandornpm run review -- --theme brand.- 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, patcheddeck.spec.yaml(pattern/layout/title-hero fields), matching slide TSX, andsrc/slides/generated/from-pack.ts(recipes also land instyle-import/pack-<id>/). Thennpm run spec. When the user likes the current look,save/updatea pack. Sibling:skills/style-library/SKILL.md. - Build the slides from the approved spec. Run
npm run specto validate and emit stubs forstatus: stubintosrc/slides/generated/from-spec.tsx. Promote each stub intosrc/slides/NN-id.tsx, setstatus: lockedin the YAML, and register the polished module insrc/slides/index.ts(see promote/merge inreferences/deck-spec.md— regenerating must not wipe locked slides). Add sources tosrc/slides/sources.ts. Copy patterns fromtemplate/src/slides/*and followreferences/design-guide.mdandreferences/layout-guide.md. For architecture or flow visuals, openreferences/diagram-guide.md. For data charts beyond a simple bar comparison, openreferences/chart-guide.md. When the user provides images, logos, screenshots or says "use this asset", followreferences/media-guide.mdend-to-end. Usenpm run devornpm run livewhile polishing — see Live mode below. - Screenshots and review. Run
npm run review. It builds the deck, screenshots every slide in its final state intoreview/, writesreview/contact-sheet.pngandreview/report.md, and exits non-zero on errors. - Critique (slide-reviewer). Run
npm run critique(sibling skillskills/slide-reviewer/). It writesreview/critique.mdfrom 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. - Self-review + fixes. Go through
references/review-checklist.mdand any user-approved critique items. Fix, then re-runnpm run reviewandnpm run critiqueuntil lint has 0 errors and the critique is accepted (or they skip). Usenpm run review -- --stepsfor click-steps. - Export. Run
npm run export:pdf, which writesexport/deck.pdfwith vector, selectable text. If blur or glow effects print wrong, also runnpm run export:pdf -- --rasterforexport/deck-raster.pdf.npm run export:pngwrites PNGs toexport/png/.npm run verifyruns the token check, typecheck, build, review and PDF export in one go. - Hand-off. Give the user the PDF, the contact sheet, how to present (
npm run dev, or opendist/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) — seereferences/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=finalrenders one slide for screenshots, and?printrenders all slides for PDF. In both, motion is off and every step is shown.- Click steps: set
steps: non 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:
BarChartfor 3–7 bar comparisons;EChart(lazy-loaded ECharts, SVG, themed from tokens) for trends, stacked part-to-whole, distributions, scatter, sankey and heatmaps. Readreferences/chart-guide.mdbefore 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. Readreferences/diagram-guide.mdbefore drawing — Mermaid for ≤8-node flows; React+CSS for swimlanes, C4 and sequences. Prop tables are inreferences/slide-catalog.md. - Motion follows the viewer's
prefers-reduced-motionsetting throughMotionConfig 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:
- Copy the file to
public/media/<kebab-name>.<ext>in the deck. - Add
<Figure src="/media/…" alt="…" cite="…" />(orillustrative) on the slide. - Run
npm run reviewand 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
content/deck.spec.yaml— editable middle layer and approval gate (references/deck-spec.md). User edits design; agent setsapproved: trueonly after explicit approval, thennpm run spec(validate + stub generate).status: lockedslides are never overwritten.npm run dev— Vite present mode at http://127.0.0.1:5173 with HMR. Edit anysrc/slides/*.tsx,sources.ts, theme CSS, or diagram component; the browser updates immediately. Keys: ←/→, Space, N notes, O overview, F fullscreen.npm run live— same as dev, plus watches the optional lightcontent/deck.outline.md→from-outline.tsx. Prefer the YAML spec; sync a light outline withnpm run spec -- --sync-outline. UncommentspecSlides/outlineSlidesinindex.tsonly 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(seediagram-guide.md), and still split if a swimlane exceeds 6 layers or 5 cells. - Don't use
position: absolutefor everyday content (SlideFrame chrome,.bg, and title.title-backdrop/.title-scrimonly). Title openers: left hero + optional full-bleedbackdrop(not centered). Prefer Grid/Flex perreferences/layout-guide.md. Don't use raw hex colors (in slides or in anEChartoption), hotlinked images you don't have rights to, invented logos, stock "AI brain" art, or pie or 3D charts. Put user media inpublic/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 overstatus: lockedslides.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

