demo-video

---
name: demo-video
description: Use when the user asks to create a demo video, product walkthrough, feature showcase, animated presentation, or marketing video from screenshots or scene descriptions.
category: Engineering
version: 1.0.0
tools: []
---

# Demo Video

Plan and script polished demo videos like a video producer, not a slideshow maker — every frame has a job, every second earns the next.

## When to Use

- User asks to create a demo video, product walkthrough, or feature showcase
- User wants an animated presentation, marketing video, or product teaser
- User wants to turn screenshots or UI captures into a polished video or GIF script
- User says "make a video", "create a demo", "record a demo", "promo video"

## Core Workflow

### 1. Pick a story structure

**The Classic Demo (30-60s):** Hook (3s) → Problem (5s) → Magic Moment (5s) → Proof (15s) → Social Proof (4s) → Invite (4s)

**The Problem-Solution (20-40s):** Before (6s) → After (6s) → How (10s) → CTA (4s)

**The 15-Second Teaser:** Hook (2s) → Demo (8s) → Logo (3s) → Tagline (2s)

### 2. Design scenes

If no screenshots are provided:
- For CLI/terminal tools: describe terminal-style dark scenes, monospace font, animated typing effect
- For conceptual demos: use text-heavy scenes with a clear color language and typography system
- Ask the user for screenshots only if the product is visual and descriptions are insufficient

Every scene has exactly ONE primary focus:
- Title scenes: product name
- Problem scenes: the pain (red, chaotic)
- Solution scenes: the result (green, spacious)
- Feature scenes: the highlighted screenshot region
- End scenes: URL / CTA button

### 3. Write narration

- One idea per scene — if you need "and" you need two scenes
- Lead with the verb: "Organize your tabs," not "Tab organization is provided."
- No jargon: "Your tabs organize themselves," not "AI-powered tab categorization."
- Use contrast: "24 tabs. One click. 5 groups."

## Output

Produce a scene-by-scene shot list and narration script the user (or their video tooling) can execute directly:

1. **Scene list** — one entry per scene: visual description, primary focus, duration
2. **Narration script** — one line per scene, timed to match
3. **Manifest** — scenes in order with durations and narration text, ready to hand to a rendering pipeline

## Scene Design System

Color language: pick one accent color for "problem" (red/chaotic) and one for "solution" (calm/spacious); keep every other scene neutral so the accent carries meaning. Typography: one display font for titles, one body font for narration captions — never more than two. Animation: use a spring curve (`cubic-bezier(0.16, 1, 0.3, 1)`), never linear or default ease. Pacing: hooks run ~3s, proof/demo beats run 8-15s, CTAs run ~4s — vary duration by content weight, not a fixed per-scene length.

## Quality Checklist

- [ ] Script includes a narration line for every scene
- [ ] Every scene has one clear focus point
- [ ] First 3 seconds grab attention
- [ ] End card has a URL and CTA
- [ ] No two consecutive scenes share the same duration and pacing

## Anti-Patterns

| Anti-pattern | Fix |
|---|---|
| Slideshow pacing — every scene the same duration | Vary durations: hooks 3s, proof 8s, CTA 4s |
| Wall of text on screen | Move info to narration, simplify visuals |
| Generic narration — "This feature lets you..." | Use specific numbers and concrete verbs |
| No story arc — just listing features | Use problem → solution → proof structure |
| Raw screenshots | Always add rounded corners, shadows, dark background |
| Using `ease` or `linear` animations | Use a spring curve: `cubic-bezier(0.16, 1, 0.3, 1)` |