Slidev Presentation Manager

Each presentation is an independent Git repo, stored locally at <SLIDES_DIR>/<name>/ and published to github.com/<GITHUB_USER>/<name>. Deployment to GitHub Pages happens automatically via GitHub Actions on every push to main.

Configuration

Edit these values to match your setup. Claude reads them at runtime — references to <GITHUB_USER>, <SLIDES_DIR>, and <DEFAULT_VISIBILITY> throughout this skill resolve from this table.

Templates location: <this skill folder>/templates/ (relative to wherever you installed the skill).

Commands

No arguments

If $ARGUMENTS is empty or list, show:

1. List folders under <SLIDES_DIR>/.
2. For each, show whether it has a .git/ and a configured remote.
3. Table:

Presentations (X)

| Name | Local | GitHub | Last edit |
|------|-------|--------|-----------|
| my-deck | ✓ | ✓ | 2026-06-02 |

Show available commands at the end.

Command: create

Trigger: /slide-creator create <name> [--public|--private]

Scaffold the deck + npm install + git init + push to GitHub + enable Pages. Defaults to <DEFAULT_VISIBILITY>. The deck starts in draft state with no palette.

→ Full 9-step flow, placeholders, gh API calls: creating.md

Command: style

Trigger: /slide-creator style <name> [palette]

Defines the deck's color palette from coolors.co (or from an existing palette). Writes palette.json (source of truth) and regenerates uno.config.ts (UnoCSS tokens + CSS variables + base rules via preflights). Never touches style.css — that file is user-owned (workarounds, typography, custom CSS).

Accepted inputs: coolors URL, coolors Object/Extended Array export, loose hexes, or no args (regenerates from palette.json).

Roles: bg / fg / primary / primary-dk / accent.

→ Full mechanics, input formats, role mapping, and how to use the palette in slides: styling.md

Command: dev

Trigger: /slide-creator dev <name>

1. Verify <SLIDES_DIR>/<name>/ exists.
2. Verify node_modules/ exists; if not, run npm install.
3. Launch the dev server in the background:

   cd <SLIDES_DIR>/<name> && npm run dev

4. Report the typical URL (http://localhost:3030) and how to stop it.

Command: build

Trigger: /slide-creator build <name>

cd <SLIDES_DIR>/<name> && npm run build

Output lands in dist/. Show total directory size when done.

Command: export

Trigger: /slide-creator export <name> [pdf|pptx|png] [options]

Exports the deck via Slidev (Playwright). Default format: pdf. Also supports pptx (PowerPoint) and png.

cd <SLIDES_DIR>/<name> && npm run export        # PDF (default)
cd <SLIDES_DIR>/<name> && npm run export:pptx   # PowerPoint

Generates the file at the deck root (slides-export.pdf / .pptx). Show the path to the generated file.

→ Formats, flags (--range, --dark, --with-clicks, --scale), note on PPTX as images, troubleshooting: exporting.md

Command: open

Trigger: /slide-creator open <name>

Open <SLIDES_DIR>/<name> in the user's editor of choice (e.g. code <SLIDES_DIR>/<name> for VS Code, zed <SLIDES_DIR>/<name> for Zed). If unsure, prefer code.

Review and approval

Every presentation is born as draft and needs ≥ 2 rounds before it can be approved. State lives in REVISIONS.md inside the deck's repo.

Commands: status (view state), review (start / continue a round), approve (release v1.0.0, gated).

→ States, REVISIONS.md schema, mechanics of each command: reviewing.md

Command: polish

Trigger: /slide-creator polish <name> [--parallel | --status]

Optional visual review, orthogonal to content review. Handles layout, typographic hierarchy, margins, font-size, element placement — everything visual except color (that's style).

Takes screenshots via slidev export --format png (alternative: browser tools), iterates slide-by-slide in sequential mode while criteria are being built, and unlocks parallel mode once there are ≥ 5 established criteria. Edits go to slides.md and optionally style.css; the slide-by-slide log lives in POLISH.md inside the deck, screenshots in polish/.

Criteria live in the skill (polish-criteria.md), not in the deck — what's learned on one deck applies to all of them. They start empty and grow with use.

→ Full flow (setup, per-slide loop, modes, integrations): polishing.md

Command: illustrate

Trigger: /slide-creator illustrate <name> [--parallel]

Optional light illustration: adds icons (Phosphor via Iconify, already integrated in Slidev) over shaped backgrounds (circle, squircle) tinted with the deck's palette. Minimalist by design — few icons, high intention, chosen for what they mean relative to the content.

Requires a defined palette (style) and is best run after polish (on a stable layout). Uses a reusable IconBadge.vue component as the single source of truth for badge styling. Like polish: screenshot-driven, sequential while conventions are being built, parallel once there are ≥ 5.

The conventions live in the skill (icon-criteria.md) — what's learned applies to every deck.

→ Full mechanics (library, component, selection, shapes, flow): illustrating.md

Command: qr

Trigger: /slide-creator qr <name> <url> [slug] [--brand] [--round] [--png]

Generates a QR code from a link and saves it inside the deck's repo (<deck>/assets/qr/<slug>.svg) as an asset ready to drop into slides.md. Optional, useful for contact, demo, or call-to-action slides.

Engine: segno (a Python dependency — see install note). Default SVG (vector). --brand tints the modules with the palette's fg (dark) role; --round gives rounded corners (card look). The asset is referenced with a relative path (./assets/qr/...) so it survives the GitHub Pages --base.

python3 <this skill folder>/generate_qr.py \
  --url "<url>" --out <SLIDES_DIR>/<name>/assets/qr/<slug>.svg \
  --dark "<hex-fg>" [--round]

Dependency: requires segno (pip install segno, or uv add segno). The --round --png combo also needs Pillow.

→ Command flow, options, slide layouts (centered, columns, card), scannability: qr.md

Rules

• Never commit node_modules/, dist/, or .local files.
• One deck = one repo. Don't nest multiple decks in a single repo.
• GitHub Pages publishes automatically via GitHub Actions on every push to main. The workflow lives in .github/workflows/deploy.yml.
• New repos default to <DEFAULT_VISIBILITY>. To flip an existing one public: gh repo edit <GITHUB_USER>/<name> --visibility public --accept-visibility-change-consequences.
• No approval without 2+ review rounds. The approve command is gated by REVISIONS.md. No bypass.