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
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- floating-ui-vue-skilldSkill
- formkit-core-skilldSkill
- motion-v-skilldSkill
- pinia-colada-skilldSkill
- pinia-skilldSkill
- primevue-skilldSkill
- quasar-skilldSkill
- reka-ui-skilldSkill
- shadcn-vue-skilldSkill
- tanstack-ai-vue-skilldSkill
- tanstack-vue-form-skilldSkill
- tanstack-vue-query-skilldSkill
- tanstack-vue-router-skilldSkill
- tanstack-vue-store-skilldSkill
- tanstack-vue-table-skilldSkill
- tanstack-vue-virtual-skilldSkill
- tresjs-core-skilldSkill
- unhead-vue-skilldSkill
- unovis-ts-skilldSkill
- unovis-vue-skilldSkill
- vee-validate-skilldSkill
- vitepress-skilldSkill
- vue-data-ui-skilldSkill
- vue-i18n-skilldSkill
- vue-router-skilldSkill
- vue-skilldSkill
- vue-test-utils-skilldSkill
- vuetify-skilldSkill
- vueuse-components-skilldSkill
- vueuse-core-skilldSkill
- vueuse-integrations-skilldSkill
- vueuse-math-skilldSkill
- vueuse-motion-skilldSkill
- vueuse-shared-skilldSkill
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
- Very specific: line 29
Run the bin directly after npm i -g @slidev/cli, or with npx.
- Very specific: line 31
Verify: after dev, slides load at http://localhost:3030.
- Very specific: line 32
After export, the PDF exists in the project root.
≈ “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
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.jsonengines). - CLI export to PDF/PNG/PPTX needs an optional peer dependency:
npm i -D playwright-chromium(package.jsonpeerDependencies, marked optional). vite-plugin-pwais 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 rootIn 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
| Task | Command |
| Dev server | slidev [entry] (entry defaults to slides.md) |
| Build SPA | slidev build [entry..] |
| Export deck | slidev export [entry..] |
| Export notes | slidev export-notes [entry..] |
| Format markdown | slidev format [entry..] |
| MCP server (stdio) | slidev mcp [entry] |
| Eject theme | slidev 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.mjsport logic). --tunnelrequires--remote(dist/cli.mjs).--per-slideis rejected with--format pptx-editable(dist/export-LauAJGMx.mjs).slidev exportprints a pointer to the browser exporter; when the dev server runs, visithttp://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
| Topic | File |
| CLI commands, flags, defaults, shortcuts | references/cli.md |
| Markdown syntax: slides, notes, imports, diagrams | references/syntax.md |
| Headmatter and per-slide frontmatter keys | references/config.md |
| Code blocks: highlighting, Monaco, Magic Move, snippets | references/code-blocks.md |
| Click animations, motion, transitions, markers, drawing | references/animations.md |
| Built-in components, layouts, global context | references/components-layouts.md |
| Export formats, build output, hosting | references/exporting.md |
| MCP server for AI agents | references/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 stepsAgent editing a live deck:
slidev & # dev server
# connect MCP client to http://localhost:3030/__mcp
# use slidev-list-slides / slidev-update-slide / slidev-insert-slideStatic site for GitHub Pages:
slidev build --base /<repo-name>/ --downloadResources
- Documentation: https://sli.dev
- Syntax guide: https://sli.dev/guide/syntax
- Theme gallery: https://sli.dev/resources/theme-gallery
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.

