Slidev Deck Generation Workflow

Problem

Slidev projects often get stuck between theme choices, addon selection, file structure, and talk rhythm. Generating one long slides.md file can turn the deck into a static content wall, while aggressive animation can distract from the message. This skill turns the official Slidev syntax reference into a maintainable production workflow: analyze the audience and content first, then decide on style, addons, and split pages.

How It Works

• Analyze before asking: read a topic, Markdown notes, meeting memo, or existing slides.md, then classify the deck as technical-talk, architecture-review, or another archetype.
• Stage the choices: ask for a visual style first, then recommend a conservative addon set based on style, content, and export needs, so the user does not need to know Slidev internals.
• Generate split pages: keep slides.md short, put slide bodies in pages/*.md, and place the first src: import inside the global headmatter to avoid a blank first slide.
• Emphasize key points: every non-cover slide should have a clear takeaway, supported by layout, contrast, v-click, v-motion, annotations, or staged reveals.
• Validate narrowly: check deck structure, src import blocks, and obvious maintainability issues, without starting servers or running full builds, exports, or tests by default.

Boundaries

It fits demos, tutorials, architecture reviews, research reports, and workshops. It is not intended for native editable PPTX delivery. If the user asks for a static export-first deck, a dev server, or full builds, those actions should be requested explicitly.