text-to-slidev

Convert technical notes, documentation, and text into Slidev presentations using @alexop/slidev-theme-brand. Use when asked to create slides, presentations, convert notes to slides, turn documentation into a talk, or generate a slidev deck. Triggers: "create presentation", "make slides", "convert to slidev", "slides from", "turn into a talk", "presentation from".

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill automates the transformation of technical notes, documentation, and raw text into professional Slidev presentations. Following a 'diagram-first' philosophy, it prioritizes visual communication over heavy text, utilizing Mermaid diagrams, syntax-highlighted code blocks, and minimal layouts to create high-impact decks for developers and technical speakers.

Use Cases

  • Technical Documentation to Slides: Seamlessly convert complex README files, API specs, or technical guides into structured, presentation-ready Slidev decks.
  • Architecture & Flow Visualization: Automatically generate Mermaid flowcharts, sequence diagrams, and state diagrams from text descriptions to explain system architectures visually.
  • Developer Workshops: Create code-centric presentations with advanced features like line highlighting and 'Magic Move' transitions for live coding or technical training sessions.
  • Rapid Talk Prototyping: Turn raw brainstorming notes or meeting summaries into a polished, brand-consistent talk using specialized layouts like 'fact', 'statement', and 'two-cols'.
nametext-to-slidev
descriptionConvert technical notes, documentation, and text into Slidev presentations using @alexop/slidev-theme-brand. Use when asked to create slides, presentations, convert notes to slides, turn documentation into a talk, or generate a slidev deck. Triggers: "create presentation", "make slides", "convert to slidev", "slides from", "turn into a talk", "presentation from".

Text to Slidev Converter

Convert technical text into diagram-first, minimal-text Slidev presentations.

IMPORTANT: Load References First

Before generating slides, read the reference files for available layouts, components, and advanced features:

Core Philosophy

"You are the content. Your slides are your Table of Contents."

  • Diagrams replace text — a good diagram replaces 200+ words
  • One concept per slide — if you need "and", split it
  • Speaker provides context; slides provide visual anchors
  • Max 3-4 bullet points — prefer a diagram instead

Required Frontmatter

---
theme: '@alexop/slidev-theme-brand'
addons:
  - '@alexop/slidev-addon-utils'
title: [Generated Title]
layout: cover
---

Workflow

  1. Read references - Load layout/component/advanced docs
  2. Analyze - Identify concepts that can be visualized
  3. Diagram First - Ask: "Can this be a flowchart, sequence, or architecture diagram?"
  4. Minimize Text - Short phrases, not sentences
  5. Structure - Intro (cover) → body → conclusion (section)

Diagram-First Approach

Content Type Use
Process/workflow flowchart LR or TD
API calls, interactions sequenceDiagram
System architecture flowchart with subgraphs
Data relationships erDiagram
State transitions stateDiagram-v2

See references/advanced.md for Mermaid syntax and examples.

Quick Layout Reference

Pattern Layout
Title slide cover
New section section
Diagram/content default
Side-by-side two-cols
Single metric fact
Bold statement statement
Closing section or end

See references/layouts.md for complete documentation.

Key Rules

Do:

  • One diagram per slide with short title (3-5 words)
  • Use line highlighting for code: ts {1|3-4|all}
  • Progressive reveal with <VClicks> (max 4 items)

Don't:

  • Bullet lists explaining processes → use flowchart
  • Paragraphs about architecture → use diagram
  • Full sentences on slides → use 2-3 word phrases
  • Diagram + long explanation → diagram + title only

Example Transformation

Input: "When a user logs in, the frontend sends credentials to the auth service, which validates them against the database and returns a JWT token."

Output:

# Login Flow

```mermaid
sequenceDiagram
  participant F as Frontend
  participant A as Auth Service
  participant D as Database
  F->>A: POST /login
  A->>D: Validate
  D-->>A: User found
  A-->>F: {token}

No bullet points. The diagram IS the explanation.