agentleFS
jasonli0226jasonli0226/pi-slides-skill/skills/web-slides/SKILL.md

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

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. olddonkey/olddonkey-skills★ 17same name
    2. 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.

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
  1. Very specific:

    Consistent icons: Use only lucide-react through <Icon>, <Card icon> or <IconList>.

    line 24
  2. Very specific:

    No template leftovers: Delete every example slide you do not use.

    line 25
  3. Very specific:

    Theme by tokens only: Every color, font and size lives in src/theme/tokens.css.

    line 26
  4. Very specific:

    Follow these steps in order, and stop at the approval gate.

    line 32
  5. Very specific:

    Scaffold: Run node scripts/new-deck.mjs <dir> --title "<takeaway title>" [--theme …

    line 37
  6. Distinctive:

    Style import (only when the user supplies a new brand): Prefer built-in / inspiration presets from step 1.

    line 38
  7. Very specific:

    Screenshots and review: Run npm run review. It builds the deck, screenshots every slide in its final state into review/, writes …

    line 46
  8. Very specific:

    Export: Run npm run export:pdf, which writes export/deck.pdf with vector, selectable text.

    line 49
  9. Distinctive:

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

    line 64
  10. Very specific:

    Add <Figure src="/media/…" alt="…" cite="…" /> (or illustrative) on the slide.

    line 67
  11. Very specific:

    Run npm run review and confirm the screenshot shows the asset.

    line 68
  12. Distinctive:

    Do not treat stubs as final deck quality.

    line 90
  13. Very specific:

    Don't put more than about 40 words of body text on a slide.

    line 94
  14. Very specific:

    Don't ship style-import/captures/* or any third-party screenshot, logo or font file.

    line 97
  15. Very specific:

    Don't skip the design-spec approval gate (content/deck.spec.yaml) or the screenshot review.

    line 98

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

InputCommandOutput
URLnpm run style:url -- https://…spec, reference captures (gitignored), brand.css with colors, fonts and layout tokens
Imagesnpm run style:images -- ./refsk-means palette, mood, brand.css (--copy puts owned images in public/media/imported/)
SVGsnpm run style:svg -- ./artpalette, 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.