10 decks you can ship today with the Claude Slidev skill

The prompt

Use the slidev skill to convert ./RFC-edge-cache.md into a 10-slide deck: title, problem, options-considered, proposal, trade-offs, rollout, risks, alternatives, open questions, decision-asked. Use the 'section' layout for dividers, 'two-cols' for trade-offs, max 5 bullets per slide, headings <=60 chars. Write to slides.md.

What slides.md looks like

---
theme: default
title: RFC - Edge Cache Migration
highlighter: shiki
transition: slide-left
---

# RFC - Edge Cache Migration

The case for moving session reads to Cloudflare KV

---
layout: section
---

# The problem

---
layout: two-cols
---

# Keep Redis

<v-clicks>

- Predictable p99
- Mature ops runbook
- One region only
</v-clicks>

::right::

# Move to KV

<v-clicks>

- Reads at edge
- 5x cheaper at scale
- Eventual consistency
</v-clicks>

Pairs with

The prompt

Use the slidev skill to write a 12-slide postmortem deck for the 2026-04-22 checkout outage. Sections: cover, impact, timeline (use 'two-cols' with v-clicks for hour-by-hour reveal), what-went-right, what-went-wrong, root-cause, contributing-factors, action-items (with owners), follow-ups, lessons, questions. Tone: blameless. Save to postmortem.md.

What slides.md looks like

---
theme: default
title: Postmortem - Checkout Outage 2026-04-22
class: text-center
---

# Checkout Outage

2026-04-22 - 47 min - blameless review

---
layout: section
---

# Timeline

---
layout: two-cols
---

# 14:02 -> 14:49 UTC

<v-clicks>

- 14:02 deploy of [email protected]
- 14:07 first 500s in Datadog
- 14:11 page fires to oncall
- 14:23 rollback initiated
- 14:49 traffic recovered
</v-clicks>

::right::

# Impact

- 12,400 failed checkouts
- $84k revenue at risk
- 0 data loss

Pairs with

The prompt

Use the slidev skill to render ./adr/0023-postgres-vs-dynamodb.md as an 8-slide ADR readout: title, context, decision, consequences-positive, consequences-negative, alternatives-considered, status, follow-ups. Use 'quote' layout for the decision sentence and 'two-cols' for consequences. Save to adr-0023.md.

What slides.md looks like

---
theme: default
title: ADR-0023 - Postgres vs DynamoDB
---

# ADR-0023

Primary store for the user-events service

---
layout: quote
---

> We will use Postgres with logical partitioning.
> Status: ACCEPTED. 2026-04-15.

---
layout: two-cols
---

# Positive

- Joins on user_id stay simple
- Existing ops runbook
- Lower fixed cost <500 GB

::right::

# Negative

- Manual sharding past 2 TB
- No native TTL on rows

Pairs with

The prompt

Use the slidev skill plus the Linear MCP to build a sprint review deck for cycle 47. Slides: cover, sprint-goal, shipped (one slide per epic, max 5 issues each), in-progress, slipped (with reasons), demo-pointers, metrics (cycle time, throughput), next-sprint-priorities, q-and-a. Use 'section' for dividers and short bullets. Save to sprint-47.md.

What slides.md looks like

---
theme: default
title: Sprint 47 Review
class: text-center
---

# Sprint 47

Apr 14 - Apr 26 - team payments

---
layout: section
---

# Shipped

---

# Epic - Refund flow v2

<v-clicks>

- PAY-1284 partial-refund API
- PAY-1291 admin UI cutover
- PAY-1297 idempotency keys
- PAY-1302 audit log export
</v-clicks>

<!-- Pull these from Linear cycle 47, status: Done -->

Pairs with

The prompt

Use the slidev skill to build a 25-slide workshop deck on 'Async Rust for backend devs'. Use 4 'section' layouts as chapter dividers: setup, ownership, futures, exercise. Include 3 Monaco-runnable code blocks ({monaco-run}) and one v-clicks code-walkthrough where lines reveal in order. End with 'layout: end'. Save to workshop-async-rust.md.

What slides.md looks like

---
theme: seriph
title: Async Rust for Backend Devs
highlighter: shiki
transition: slide-left
---

# Async Rust

A 60-minute hands-on workshop

---
layout: section
---

# 3. Futures

---

# A future is a state machine

```rust {monaco-run}
async fn fetch_user(id: u64) -> Result<User, Error> {
    let row = sqlx::query!("SELECT * FROM users WHERE id = $1", id)
        .fetch_one(&pool)
        .await?;
    Ok(row.into())
}
```

<!-- Click 'Run' to see the desugared poll() output -->

Pairs with

The prompt

Use the slidev skill to author a 22-slide conference talk: 'Why your build is 12x slower than it needs to be'. Structure: cover, hook (a single number), 3 'section' dividers, 4 code-comparison slides ({2,4-6} highlighting), 2 'quote' slides for the takeaway lines, mid-talk demo placeholder, 'fact' slide with the punchline, end. Save to talk-build-perf.md.

What slides.md looks like

---
theme: seriph
title: Why Your Build Is 12x Slower
class: text-center
background: https://cover.sli.dev
---

# Why Your Build Is 12x Slower

Anthony Tran  -  ViteConf 2026

---
layout: fact
---

# 47 seconds

what we cut from cold start

---
layout: quote
---

> "Bundlers don't make builds slow.
> Imports do."

---

```ts {2,4-6}
import { z } from 'zod'
import * as utils from './utils'   // 800 named exports
import { fetcher } from '@/lib/api'
import * as date from './date'      // 1400 LOC barrel
import * as fmt from './format'
import { Modal } from '@/ui/modal'
```

Pairs with

The prompt

Use the slidev skill to draft a 12-slide internal tech talk: 'How our feature flag service handles 800k QPS'. Tone: casual. 1 cover, 1 'fact' slide for the QPS number, 4 architecture slides (with two-cols: claim on left, code on right), 2 v-clicks gotcha slides, 1 numbers slide, 3 'what we'd do differently' slides. No formal end. Save to lunch-flags.md.

What slides.md looks like

---
theme: default
title: 800k QPS Feature Flags
---

# 800k QPS feature flags

How the flagsd service holds up - 12 slides, lunch ends in 25 min

---
layout: fact
---

# 800,000 / sec

p99 read latency: 0.4 ms

---
layout: two-cols
---

# Claim

The hot path never hits Redis.

::right::

# Code

```go {3,5}
func (s *Server) Eval(ctx context.Context, key string) bool {
    if v, ok := s.local.Load(key); ok {
        return v.(bool)            // 99.97% of calls land here
    }
    return s.fetchAndCache(ctx, key)
}
```

Pairs with

The prompt

Use the slidev skill to write a 10-slide launch deck for 'Workspace Search v2'. Slides: cover, the-tweet (one-sentence promise on a 'fact' layout), problem, what-shipped, demo-placeholder (image-right layout), metrics-we-track, 30-day-targets, who-helped, what-we-killed, what's-next. Save to launch-search-v2.md.

What slides.md looks like

---
theme: default
title: Workspace Search v2 - Launch
class: text-center
---

# Workspace Search v2

Shipped 2026-04-29 - 10-slide launch readout

---
layout: fact
---

# Find anything in 80 ms

across docs, threads, tickets

---
layout: image-right
image: /screenshots/search-v2-hero.png
---

# What it does

<v-clicks>

- Unified index across 6 sources
- Ranks by recency + your graph
- Keyboard-first, mouse optional
- Free for all paid plans
</v-clicks>

Pairs with

The prompt

Use the slidev skill to build a 30-slide onboarding deck for new backend hires. Sections (each behind a 'section' layout): orientation, system-map, codebase-tour, how-we-ship, first-week-checklist, mentors-and-channels. Embed the system architecture as a Mermaid diagram. Add presenter notes on every slide. Save to onboarding-backend.md.

What slides.md looks like

---
theme: default
title: Backend Onboarding - Week 1
---

# Welcome to the backend team

Week 1 - 30 slides - your mentor walks you through this on day 2

<!-- Hand the laptop to the new hire after slide 5; they drive the rest. -->

---
layout: section
---

# 2. System map

---

# How requests flow

```mermaid
sequenceDiagram
    Client->>Edge: POST /checkout
    Edge->>API: forward
    API->>Postgres: write order
    API->>Queue: emit order.created
    Queue->>Worker: charge card
```

<!-- Spend 4 min here. Most new hires confuse Edge with API on day 2. -->

Pairs with

The prompt

Use the slidev skill to write a 14-slide internal pitch deck for 'devbox' - a self-hosted dev environment service. Slides: cover, the-ask (1 sentence on 'fact' layout), today's-pain (with metrics), proposed-solution, demo, before/after numbers, cost-breakdown (table), team-needed, milestones (3-month, 6-month), risks, asks-of-this-room, FAQ, end. Save to pitch-devbox.md.

What slides.md looks like

---
theme: default
title: devbox - Internal Pitch
class: text-center
---

# devbox

A self-hosted dev environment service - 14-slide pitch

---
layout: fact
---

# 2 engineers, 1 quarter

what we need to ship the MVP

---

# Cost breakdown

| Item             | Year 1   | Year 2   |
|------------------|----------|----------|
| 2 engineers      | $480k    | $520k    |
| AWS (EC2 + EBS)  | $84k     | $140k    |
| Total            | $564k    | $660k    |

<v-click>

Net savings vs status-quo: **$1.1M / year** at 200 active devs.

</v-click>

Pairs with