agentleFS
skilld-devskilld-dev/vue-ecosystem-skills/skills/slidev-cli-skilld/SKILL.md

slidev-cli-skilld

Skill184 starsChanged 37 days agoMITView on GitHub

Build, present, and ship Slidev decks with @slidev/cli. Use when scaffolding a Slidev project, writing or editing slides.md Markdown decks, running the dev server, adding code highlighting, animations, layouts, or Vue components, exporting to PDF/PPTX/PNG/Markdown, building a hostable SPA, or driving slides through the built-in MCP server.

  • Installs packages

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the bin directly after npm i -g @slidev/cli, or with npx.

    line 29
  2. Very specific:

    Verify: after dev, slides load at http://localhost:3030.

    line 31
  3. Very specific:

    After export, the PDF exists in the project root.

    line 32

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

Slidev CLI (@slidev/cli v53.0.0)

Markdown slides for developers, built on Vite, Vue 3, UnoCSS, and Shiki. Verified against the prepared @slidev/cli 53.0.0 package source.

Environment limits

  • Node.js >= 22.12.0 (package.json engines).
  • CLI export to PDF/PNG/PPTX needs an optional peer dependency: npm i -D playwright-chromium (package.json peerDependencies, marked optional).
  • vite-plugin-pwa is an optional peer dependency for PWA output.

Quick start

npm init slidev        # scaffold a project (README.md); pnpm create slidev also works
npm run dev            # dev server on http://localhost:3030
npm run build          # static SPA into dist/
npm run export         # PDF into the project root

In a scaffolded project, dev/build/export scripts wrap the slidev bin. Run the bin directly after npm i -g @slidev/cli, or with npx.

Verify: after dev, slides load at http://localhost:3030. After export, the PDF exists in the project root.

Commands

TaskCommand
Dev serverslidev [entry] (entry defaults to slides.md)
Build SPAslidev build [entry..]
Export deckslidev export [entry..]
Export notesslidev export-notes [entry..]
Format markdownslidev format [entry..]
MCP server (stdio)slidev mcp [entry]
Eject themeslidev theme eject [entry]

Full flags and defaults: references/cli.md

Smallest working deck

---
theme: default
title: My Talk
transition: slide-left
---

# First slide

Content

---

# Second slide

<!--
Presenter notes: the last HTML comment of a slide.
-->
  • --- separates slides; blank lines around it.
  • The first frontmatter block is the headmatter (deck config).
  • Later blocks are per-slide frontmatter.

Key rules

  • Dev server default port is 3030; if taken, Slidev picks another in 3030-4000 (dist/cli.mjs port logic).
  • --tunnel requires --remote (dist/cli.mjs).
  • --per-slide is rejected with --format pptx-editable (dist/export-LauAJGMx.mjs).
  • slidev export prints a pointer to the browser exporter; when the dev server runs, visit http://localhost:<port>/export/ to export from the browser (dist/cli.mjs).
  • Editing slides programmatically: prefer the built-in MCP tools over raw text edits; they handle compound --- separators and hot-reload. See references/mcp.md.
  • Magic Move code animation needs a four-backtick wrapper fence. See references/code-blocks.md.

References

TopicFile
CLI commands, flags, defaults, shortcutsreferences/cli.md
Markdown syntax: slides, notes, imports, diagramsreferences/syntax.md
Headmatter and per-slide frontmatter keysreferences/config.md
Code blocks: highlighting, Monaco, Magic Move, snippetsreferences/code-blocks.md
Click animations, motion, transitions, markers, drawingreferences/animations.md
Built-in components, layouts, global contextreferences/components-layouts.md
Export formats, build output, hostingreferences/exporting.md
MCP server for AI agentsreferences/mcp.md

Common workflows

New deck, iterate, export PDF:

npm init slidev
slidev                       # dev server, edit slides.md, check localhost:3030
npm i -D playwright-chromium # once, for CLI export
slidev export --with-clicks  # PDF including click steps

Agent editing a live deck:

slidev &                     # dev server
# connect MCP client to http://localhost:3030/__mcp
# use slidev-list-slides / slidev-update-slide / slidev-insert-slide

Static site for GitHub Pages:

slidev build --base /<repo-name>/ --download

Resources

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.