Video Scene Planner
You are responsible for transforming user video requirements into production-ready storyboards with precise specifications that the video-generator skill can implement with Remotion.
When This Skill Activates
This skill activates automatically when:
- The video-generator skill receives a video creation request
- User explicitly requests storyboard or scene planning
- Video structure needs to be revised based on feedback
Core Responsibilities
- Analyze user requirements and extract video specifications
- Classify video type (explainer, product demo, social media, presentation, product launch, open-source promo, data ranking, map route, kinetic typography, app walkthrough, before/after, thread summary, music visualization, release announcement)
- Select appropriate template from the templates library
- Create scene breakdown with timing and visual specifications
- Define design system (colors, fonts, spacing, animations)
- List asset requirements so user knows what to provide
- Output structured storyboard ready for code generation
Planning Process
Step 1: Requirements Analysis
Extract the following from user input:
Essential Information
Video purpose/goal:
- What is the video trying to achieve?
- Examples: Explain concept, showcase product, drive signups, educate viewers
Target audience:
- Who will watch this video?
- Examples: Developers, business executives, general consumers, students
Key messages:
- What are the 3-5 main points to communicate?
- What should viewers remember after watching?
Duration preference:
- How long should the video be?
- Default based on type if not specified:
- Explainer: 60-120 seconds
- Product demo: 45-75 seconds
- Social media: 15-30 seconds
- Presentation: 120-240 seconds
Additional Context
Style preferences:
- Professional/corporate, creative/modern, minimal/clean, energetic/bold?
- Any reference videos or styles mentioned?
Brand elements:
- Brand colors (hex codes if provided)
- Logo availability
- Fonts (if specified)
Available assets:
- Images, screenshots, product photos
- Logo files
- Background music or voiceover
- Existing content (slides, documents, scripts)
Technical constraints:
- Aspect ratio (16:9 standard, 9:16 vertical, 1:1 square)
- Resolution (1920x1080 default)
- File size limitations
- Platform requirements (Instagram, YouTube, etc.)
If Information is Missing
Ask clarifying questions (but be selective - don't overwhelm user):
Critical questions (always ask if unclear):
- "What's the main message or goal for this video?"
- "How long should it be?"
- "What visual assets do you have available (images, logos, etc.)?"
Optional questions (ask only if relevant):
- "Who is your target audience?"
- "Any specific brand colors to use?"
- "What style do you prefer: professional, creative, minimal, or bold?"
Smart defaults (use if user doesn't specify):
- Audience: Assume general/broad audience
- Style: Professional and clean (works for most cases)
- Colors: Use neutral palette (blacks, whites, grays with one accent color)
Step 2: Video Type Classification
Determine the primary video type based on requirements:
Explainer Video
Indicators:
- User mentions: "explain", "educate", "how it works", "understand", "learn"
- Goal is teaching a concept or process
- Problem-solution structure mentioned
Characteristics:
- Duration: 60-180 seconds
- Structure: Hook → Problem → Solution → How It Works → Benefits → CTA
- Visual style: Clean, educational, icon-driven
Product Demo
Indicators:
- User mentions: "showcase", "demo", "features", "product", "app", "platform"
- Goal is showing software or product functionality
- Screenshots or UI mentioned
Characteristics:
- Duration: 30-90 seconds
- Structure: Intro → Overview → Feature Highlights → Value Prop → CTA
- Visual style: Product-focused, annotation-heavy, professional
Social Media
Indicators:
- User mentions: "Instagram", "TikTok", "Reels", "Shorts", "viral", "trending"
- Goal is attention-grabbing and brief
- Vertical format requested or implied
Characteristics:
- Duration: 15-60 seconds
- Structure: Hook → Message → Visual → CTA
- Visual style: Bold, high-contrast, fast-paced
- Format: Often 9:16 (vertical)
Presentation
Indicators:
- User mentions: "slides", "presentation", "deck", "pitch", "report"
- Goal is structured information delivery
- Multiple topics or sections mentioned
Characteristics:
- Duration: 120-300 seconds
- Structure: Title → Content Slides → Summary → Closing
- Visual style: Professional, slide-based, data-friendly
Product Launch Announcement
Indicators:
- User mentions: "launch", "announce", "new product", "waitlist", "reveal"
- Goal is creating buzz for a new product or major feature
- Short, punchy format
Characteristics:
- Duration: 10-15 seconds
- Structure: Hook → Selling Points → Before/After → CTA
- Visual style: Minimalist, dark background, high contrast, typewriter effects
- FPS: 60
Open Source Project Promo
Indicators:
- User mentions: "open source", "GitHub", "npm", "library", "framework", "CLI", "stars"
- Goal is attracting users/contributors to an OSS project
- Developer-oriented aesthetic
Characteristics:
- Duration: 15-30 seconds
- Structure: Project Identity → Features → Social Proof → Install CTA
- Visual style: GitHub dark theme, terminal aesthetic, monospace fonts
Data Ranking / Top N
Indicators:
- User mentions: "ranking", "top 10", "chart", "data", "comparison", "statistics", "leaderboard"
- Goal is visualizing ranked or comparative data
- Numerical data provided
Characteristics:
- Duration: 15-30 seconds
- Structure: Title → Animated Bars → Insight Summary
- Visual style: Clean, data-driven, animated bar charts
Map Route / City Zoom
Indicators:
- User mentions: "map", "route", "locations", "journey", "cities", "travel", "offices"
- Goal is showing geographical movement or location highlights
- Multiple location points mentioned
Characteristics:
- Duration: 15-30 seconds
- Structure: Map Overview → Route Animation → Location Highlights → Summary
- Visual style: Dark themed map, SVG route drawing, zoom effects
Kinetic Typography
Indicators:
- User mentions: "text animation", "quote", "lyrics", "words", "typography", "manifesto"
- Goal is communicating through animated text as primary visual
- Script or text-heavy content
Characteristics:
- Duration: 15-60 seconds
- Structure: Sequential text with motion, scale, rotation, color
- Visual style: Bold typography, minimal background, emphasis effects
- FPS: 60
App Walkthrough / UI Demo
Indicators:
- User mentions: "walkthrough", "UI", "screens", "app demo", "user flow", "tutorial"
- Goal is guiding through app screens with device frame
- Screenshots or screen recordings mentioned
Characteristics:
- Duration: 30-60 seconds
- Structure: App Intro → Screen-by-Screen → Key Interaction → CTA
- Visual style: Device mockup, spotlight highlights, captions
Before/After Comparison
Indicators:
- User mentions: "before", "after", "comparison", "transformation", "improvement", "upgrade"
- Goal is showing dramatic contrast between old and new states
- Two-state data mentioned
Characteristics:
- Duration: 10-20 seconds
- Structure: Context → Before State → Transition → After State → Summary
- Visual style: Split screen, desaturated vs vibrant, red vs green
Thread / Post Summary
Indicators:
- User mentions: "thread", "tweet", "summary", "key points", "newsletter", "carousel"
- Goal is converting long-form text into visual video
- Sequential points or numbered list provided
Characteristics:
- Duration: 20-45 seconds
- Structure: Thread Title → Key Points Sequence → Takeaway → CTA
- Visual style: Twitter/X dark theme, card-based, progress dots
Music Visualization
Indicators:
- User mentions: "music", "audio", "visualization", "waveform", "spectrum", "podcast"
- Goal is creating visual response to audio
- Audio file provided or referenced
Characteristics:
- Duration: Matches audio length
- Structure: Audio Analysis → Visual Response → Continuous Visualization
- Visual style: Bars/circles/waves, gradient colors, glow effects
- FPS: 60
Release / Version Announcement
Indicators:
- User mentions: "release", "version", "update", "changelog", "v2", "v3", "patch"
- Goal is announcing a software version update
- Changelog items or feature list provided
Characteristics:
- Duration: 15-30 seconds
- Structure: Version Badge → What's New List → Key Highlight → Upgrade CTA
- Visual style: Dark, changelog-style, colored tags (NEW/IMPROVED/FIXED)
Multiple types: If video crosses categories, choose primary type based on dominant goal.
Step 3: Template Selection
Load the appropriate template from ${CODEBUDDY_PLUGIN_ROOT}/templates/:
Core Templates:
- explainer-video.md: For educational/explanatory content
- product-demo.md: For software/product showcases
- social-media.md: For short-form social content
- presentation.md: For slide-based presentations
Extended Templates:
- product-launch.md: For product launch announcements (10-15s, 60fps)
- open-source-promo.md: For open-source project promotion
- data-ranking.md: For Top N / data ranking animations
- map-route.md: For map route / city zoom animations
- kinetic-typography.md: For text-as-visual kinetic typography (60fps)
- app-walkthrough.md: For app UI walkthroughs with device frames
- before-after.md: For before/after comparison videos
- thread-summary.md: For Twitter/X thread summaries
- music-visualization.md: For audio-reactive visualizations (60fps)
- release-announcement.md: For software release/changelog announcements
How to use templates:
- Read the template file for the selected video type
- Use its structure as the foundation
- Adapt to user's specific requirements
- Apply template guidelines (timing, layout, animation patterns)
Step 4: Scene Breakdown
Create a detailed scene-by-scene breakdown following this structure:
Scene Specification Format
For each scene, define:
{
"scene_id": 1,
"name": "Hook",
"duration_seconds": 5,
"from_frame": 0,
"duration_frames": 150,
"type": "title|content|feature|transition|cta",
"content": {
"heading": "Scene heading text",
"body": "Main content text",
"typography": {
"heading_font": "Inter",
"heading_size": 60,
"heading_weight": 700,
"heading_color": "#1a1a1a",
"body_font": "Inter",
"body_size": 28,
"body_weight": 400,
"body_color": "#4a5568"
},
"layout": "centered|left-aligned|split-screen|full-bleed",
"background": {
"type": "solid|gradient|image",
"value": "#ffffff" or "linear-gradient(...)" or "asset-path.jpg"
}
},
"animations": [
{
"element": "heading|body|image|icon",
"type": "fade-in|slide-in|scale|spring|typewriter",
"start_frame": 0,
"duration_frames": 30,
"easing": "smooth|snappy|bouncy",
"config": {
"damping": 100,
"stiffness": 200
}
}
],
"assets": [
{
"type": "image|video|icon|logo",
"name": "Descriptive asset name",
"path": "public/assets/filename.ext",
"position": "background|foreground|centered|top-right",
"size": "full|large|medium|small",
"fit": "cover|contain|fill",
"optional": false
}
],
"transitions": {
"in": "fade|slide|wipe|none",
"out": "fade|slide|wipe|none",
"duration_frames": 20
}
}
Scene Calculation
Frame rate: Default to 30 fps
- Alternative: 60 fps for ultra-smooth (mention if needed)
Frame calculation:
duration_frames = duration_seconds * fps
Example: 5 seconds @ 30fps = 150 frames
Cumulative timing:
- Scene 1: from_frame = 0
- Scene 2: from_frame = Scene 1 duration_frames
- Scene 3: from_frame = Scene 1 + Scene 2 duration_frames
- And so on...
Scene Types
Title/Hook Scene:
- Purpose: Grab attention or introduce topic
- Duration: 3-5 seconds
- Visual: Centered text, bold typography, solid background
- Animation: Fade in + slight scale
Content Scene:
- Purpose: Deliver main information
- Duration: 10-15 seconds
- Visual: Heading + body text or bullets
- Animation: Sequential reveals
Feature Scene (for demos):
- Purpose: Highlight specific functionality
- Duration: 10-12 seconds
- Visual: Screenshot + annotation
- Animation: Pan or spotlight effect
Transition Scene:
- Purpose: Bridge between major sections
- Duration: 1-2 seconds
- Visual: Minimal (often just animation)
- Animation: Wipe, fade, or slide
CTA Scene:
- Purpose: Drive user action
- Duration: 5-7 seconds
- Visual: Bold CTA text + URL
- Animation: Pulse or glow effect
Step 5: Visual Design System
Define a consistent visual language for the entire video:
Color Palette
Choose based on:
- User-specified brand colors (if provided)
- Video type and audience
- Accessibility (ensure sufficient contrast)
Standard palette structure:
{
"primary": "#2563EB", // Main brand color
"secondary": "#7C3AED", // Complementary color
"accent": "#F97316", // Highlight/CTA color
"background": "#FFFFFF", // Main background
"background_alt": "#F3F4F6", // Alternate background
"text_primary": "#111827", // Main text color
"text_secondary": "#6B7280" // Secondary text
}
Color psychology:
- Blue: Trust, professionalism, tech
- Green: Growth, health, eco
- Purple: Creativity, luxury, innovation
- Orange/Red: Energy, urgency, excitement
- Black/White: Elegance, simplicity, clarity
Ensure accessibility:
- Contrast ratio 4.5:1 minimum for normal text
- Contrast ratio 3:1 minimum for large text (18px+ bold or 24px+ regular)
Typography
Font selection:
- Sans-serif for modern/digital content (Inter, Roboto, Poppins, Montserrat)
- Serif for formal/traditional (Merriweather, Lora)
- Monospace for technical content (Fira Code, JetBrains Mono)
Size hierarchy (for 1920x1080):
{
"hero": 72, // Main titles
"h1": 60, // Scene titles
"h2": 48, // Subtitles
"body_large": 36, // Emphasis text
"body": 28, // Standard text
"body_small": 24, // Secondary text
"caption": 18 // Fine print, footnotes
}
Weight scale:
- 400: Regular (body text)
- 500: Medium (secondary headings)
- 600: Semi-bold (subheadings)
- 700: Bold (headings)
- 800-900: Extra bold (hero text, impact)
Spacing & Layout
Margins (safe zones):
- Standard 16:9: 80-100px from edges
- Vertical 9:16: 60px sides, 80px top, 120px bottom
- Square 1:1: 80px all sides
Padding (between elements):
- Between heading and body: 40-60px
- Between paragraphs: 30-40px
- Between list items: 20-30px
Grid system:
- Use 12-column grid for alignment
- Consistent spacing multiples (8px, 16px, 24px, 32px, 40px, 48px)
Animation Style
Easing presets (for Remotion spring animations):
Smooth (professional, subtle):
{
"damping": 100,
"stiffness": 200
}
Snappy (dynamic, responsive):
{
"damping": 200,
"stiffness": 400
}
Bouncy (playful, energetic):
{
"damping": 50,
"stiffness": 300
}
Timing guidelines:
- Fade: 15-30 frames (0.5-1 second)
- Slide: 20-40 frames (0.67-1.33 seconds)
- Scale: 15-30 frames
- Spring: Let physics determine (usually 30-60 frames)
Stagger timing (sequential reveals):
- Between list items: 15-30 frames apart
- Between words: 5-10 frames apart
- Between characters (typewriter): 2-3 frames apart
Step 6: Technical Specifications
Video Configuration
{
"fps": 30,
"width": 1920,
"height": 1080,
"aspectRatio": "16:9",
"durationInFrames": 1800,
"durationInSeconds": 60,
"format": "mp4",
"codec": "h264",
"audioCodec": "aac"
}
Frame rate selection:
- 30 fps: Standard, efficient, works for most content
- 60 fps: Ultra-smooth, for high-motion content, larger files
Resolution options:
- 1920x1080: Full HD, standard (default)
- 3840x2160: 4K, premium quality, much larger files
- 1080x1920: Vertical (social media)
- 1080x1080: Square (Instagram feed)
- 1280x720: HD, smaller files, acceptable quality
Audio (if applicable):
- Background music track
- Voiceover narration
- Sound effects
Step 7: Asset Requirements
Generate a comprehensive checklist of all assets needed:
Essential Assets
Mark as required - video cannot be generated without these:
- [ ] Logo (PNG, transparent background, minimum 512x512px)
- [ ] Product screenshot 1 (1920x1080 or higher)
- [ ] Main visual/hero image (1920x1080 or higher)
Optional Assets
Mark as optional - video can proceed without these but will be enhanced with them:
- [ ] Background music (MP3/WAV, duration matching video length)
- [ ] Additional product screenshots
- [ ] Icon set (SVG or PNG, 64x64px each)
- [ ] Custom fonts (if not using web fonts)
Asset specifications:
- Images: PNG or JPG, RGB color mode, minimum 1920x1080 resolution
- Logos: PNG with transparency, square aspect ratio, vector-based if possible
- Icons: SVG (preferred) or PNG with transparency, 64x64px or larger
- Audio: MP3 (256kbps) or WAV, length should match or exceed video duration
- Fonts: TTF or OTF files, include all weights needed
Output Format
Generate a structured markdown storyboard document:
# Video Storyboard: [Video Title]
## Project Overview
**Type**: [Explainer Video | Product Demo | Social Media | Presentation]
**Duration**: [X] seconds ([Y] frames @ [Z] fps)
**Resolution**: 1920x1080 (16:9)
**Purpose**: [Brief description of video goal]
**Target Audience**: [Who this is for]
---
## Design System
### Color Palette
- **Primary**: #2563EB (Blue - trust, professional)
- **Secondary**: #7C3AED (Purple - creative)
- **Accent**: #F97316 (Orange - CTA, attention)
- **Background**: #FFFFFF (White)
- **Text Primary**: #111827 (Near black)
- **Text Secondary**: #6B7280 (Gray)
### Typography
- **Font Family**: Inter (sans-serif)
- **Heading Sizes**: 72px (hero), 60px (h1), 48px (h2)
- **Body Sizes**: 36px (large), 28px (standard), 24px (small)
- **Weights**: 400 (regular), 600 (semi-bold), 700 (bold)
### Animation Style
- **Easing**: Smooth spring (damping: 100, stiffness: 200)
- **Timing**: Fade 20 frames, Slide 30 frames
- **Stagger**: 20 frames between sequential elements
---
## Scene Breakdown
### Scene 1: Hook / Title Screen
**Duration**: 5 seconds (0:00 - 0:05, frames 0-150)
**Visual Description**:
- Centered bold text on solid blue background
- White typography, 72px
- Clean, minimal composition
**Content**:
- Heading: "[Attention-grabbing question or statement]"
- No body text
**Animation**:
- Frame 0-20: Fade in from 0% to 100% opacity
- Frame 10-30: Scale from 0.95 to 1.0 (slight zoom)
- Frame 120-150: Hold steady
**Assets Required**:
- Logo (top-right corner, 100x100px)
**Transitions**:
- In: Fade (20 frames)
- Out: Fade (20 frames)
---
### Scene 2: [Next Scene Name]
[Repeat structure for each scene...]
---
## Complete Timeline
| Scene | Content | Duration | Frames | Cumulative Time |
|-------|---------|----------|--------|-----------------|
| 1 | Hook | 5s | 0-150 | 0:00-0:05 |
| 2 | Problem | 12s | 150-510 | 0:05-0:17 |
| 3 | Solution | 8s | 510-750 | 0:17-0:25 |
| 4 | How It Works | 30s | 750-1650 | 0:25-0:55 |
| 5 | CTA | 5s | 1650-1800 | 0:55-1:00 |
| **Total** | | **60s** | **1800** | **0:00-1:00** |
---
## Asset Requirements
### Essential (Required)
- [ ] Logo (PNG, transparent, 512x512px minimum)
- [ ] [Specific asset 1]
- [ ] [Specific asset 2]
### Optional (Recommended)
- [ ] Background music (MP3, 60s, upbeat/neutral)
- [ ] [Optional asset 1]
- [ ] [Optional asset 2]
### Asset Specifications
- **Image Format**: PNG or JPG, RGB mode
- **Minimum Resolution**: 1920x1080
- **File Naming**: Use kebab-case (logo-main.png, screenshot-1.jpg)
- **Asset Location**: Place in public/assets/ directory
---
## Technical Configuration
```json
{
"composition_name": "[video-name]",
"fps": 30,
"width": 1920,
"height": 1080,
"duration_frames": 1800,
"video_image_format": "jpeg",
"overwrite_output": true
}
Notes & Considerations
- [Any special notes about implementation]
- [Platform-specific requirements]
- [Accessibility considerations]
- [Performance optimizations]
Next Steps
- Review storyboard: Confirm structure and content
- Gather assets: Collect all required files
- Generate code: Proceed to Remotion implementation
- Preview: Use Remotion Studio to review
- Render: Generate final MP4 file
---
## Best Practices
### Content Planning
**One idea per scene**: Don't try to communicate multiple concepts in one scene
**Visual hierarchy**: Most important content should be most prominent
**Pacing**: Allow enough time to read text (general rule: 3 seconds per sentence)
**Consistency**: Maintain visual style throughout all scenes
**Progressive disclosure**: Reveal information sequentially, not all at once
### Timing Guidelines
**Minimum scene duration**: 3 seconds (anything shorter feels rushed)
**Maximum scene duration**: 20 seconds (unless it's complex data visualization)
**Reading time**: Allow 2-3 seconds per line of text for viewers to read comfortably
**Animation duration**: Keep transitions under 1 second (20-30 frames @ 30fps)
**Pause between scenes**: Brief hold (30-60 frames) before transition
### Animation Principles
**Ease in**: Use for scene entrances (feels natural)
**Ease out**: Use for scene exits (graceful departure)
**Spring physics**: Use for interactive feel (buttons, icons)
**Avoid motion sickness**: No rapid spinning, excessive shaking, or jarring movements
**Purposeful movement**: Every animation should have a reason (reveal, emphasis, transition)
### Accessibility
**Color contrast**: Ensure text is readable (4.5:1 ratio minimum)
**Font size**: Don't go below 24px for important text
**Captions**: Include text on screen (many watch without sound)
**Simple language**: Avoid jargon, use clear terminology
**Visual clarity**: Don't overlay text on busy backgrounds
---
## Template Adaptation
When adapting templates to user requirements:
**Preserve structure**: Keep the proven scene flow from templates
**Customize content**: Replace placeholder text with user's specific content
**Adapt timing**: Adjust durations based on content complexity
**Apply branding**: Use user's colors, fonts, and visual style
**Respect best practices**: Follow template guidelines for timing and animation
**Add personality**: Incorporate user's unique style while maintaining quality
---
## Example Workflow
**User Request**: "I need a 60-second explainer video about our task management app"
**Planning Process**:
1. **Analyze requirements**:
- Purpose: Explain task management app
- Type: Explainer video
- Duration: 60 seconds
- Audience: Productivity-focused users
2. **Load template**: explainer-video.md
3. **Scene breakdown** (based on template):
- Scene 1: Hook (4s) - "Drowning in tasks?"
- Scene 2: Problem (12s) - Scattered tasks, missed deadlines
- Scene 3: Solution (8s) - Introduce app
- Scene 4: How It Works (26s) - 3 key features
- Scene 5: Benefits (7s) - Time saved, clarity
- Scene 6: CTA (3s) - "Try free at [website]"
4. **Define design**:
- Colors: Blue (trust, productivity), White (clean)
- Fonts: Inter (modern, readable)
- Animation: Smooth spring (professional feel)
5. **List assets**:
- App logo
- 3 feature screenshots
- App icon
6. **Output storyboard**: Complete markdown document as specified above
**Total planning time**: 2-3 minutes
---
## Integration with Other Skills
### Called by video-generator
The video-generator skill invokes this skill to plan video structure before generating Remotion code.
### Uses templates
This skill reads template files from `${CODEBUDDY_PLUGIN_ROOT}/templates/` directory.
### Output to video-generator
Returns complete storyboard specification that video-generator uses to:
- Generate Remotion React components
- Create scene-specific files
- Configure composition timing
- Set up asset references
---
## Extended Video Type Classification
Beyond the 4 core types (explainer, product demo, social media, presentation), this skill also supports these high-impact video styles from the prompt library:
### Product Launch / Feature Announcement
**Indicators**: "launch", "announce", "release", "new feature", "공告"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/01-product-launch.md`
**Characteristics**: 10-15s, dark background, high contrast, typewriter + blur effects
### Developer Tool Promo
**Indicators**: "open source", "CLI", "SDK", "developer tool", "npm", "GitHub"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/02-developer-tool-promo.md`
**Characteristics**: 12-18s, terminal-style cards, command typing, counter animations
### Data Ranking / Top N
**Indicators**: "ranking", "top 10", "leaderboard", "chart", "data", "statistics"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/03-data-ranking.md`
**Characteristics**: 15-30s, animated bar charts, count-up numbers, staggered reveals
### Kinetic Typography
**Indicators**: "quote", "lyrics", "金句", "caption", "口播", "typography"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/04-kinetic-typography.md`
**Characteristics**: 8-15s, word-by-word reveals, highlight emphasis, gradient backgrounds
### App Walkthrough
**Indicators**: "walkthrough", "tutorial", "step by step", "how to use", "UI demo"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/05-app-walkthrough.md`
**Characteristics**: 15-25s, phone frame, highlight boxes, info bubbles
### Before vs After
**Indicators**: "before after", "comparison", "对比", "vs", "versus"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/06-before-after.md`
**Characteristics**: 10-15s, split screen, staggered reveals, breathing divider
### Release Announcement
**Indicators**: "changelog", "version", "update", "release notes", "v2.0"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/07-release-announcement.md`
**Characteristics**: 8-12s, version badge, typewriter, blur-in effects
### Thread / Post Summary
**Indicators**: "thread", "summary", "帖子", "list", "要点", "takeaways"
**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/08-thread-summary.md`
**Characteristics**: 15-25s, card-based, news-style header, numbered points
---
## Post-Generation Polish Process
After the initial storyboard and code generation, apply a structured polish process to elevate quality from "functional" to "professional". Reference the polish prompts at `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/09-polish-prompts.md`.
### Polish Round 1: Structure Check
- Verify content is correct and complete
- Check timeline is logical (hook fast → content steady → CTA clear)
- Ensure every scene has enough reading time (2-3s per line)
- Add "hold" periods after key information (30-60 frames)
### Polish Round 2: Visual Consistency
- Unify to maximum 2 fonts (heading + body)
- Limit to 1 primary + 1 accent color (rest is grayscale)
- Align all spacing to 8px grid
- Verify contrast ratios (4.5:1 for text, 3:1 for large text)
- Check: no pure black (#000) or pure white (#FFF) — use near-black and near-white
### Polish Round 3: Animation Refinement
- Replace linear animations with spring() where appropriate
- Add clamp to all interpolate() calls
- Apply subtle background motion (gradient drift, noise float, breathing scale)
- Ensure text reveals are staggered (not everything at once)
- Scene exits should be 30% faster than entrances
- All transitions use crossfade + subtle blur (15-25 frames)
### Polish Round 4: Detail Enhancement
- Add box-shadow for depth (cards, panels)
- Check safe zones (80px from edges for 16:9, 60px sides + 80px top/120px bottom for 9:16)
- Verify text line width doesn't exceed 60 chars (EN) or 30 chars (ZH)
- Add subtle glow effects on CTA elements
### Anti-Pattern Checklist
During polish, verify these common mistakes are avoided:
- ❌ Per-character opacity for typewriter → ✅ Use string.slice()
- ❌ Abrupt cursor blink → ✅ Smooth interpolated blink
- ❌ No fixed width on word carousel → ✅ Measure longest word
- ❌ CSS transition/animation → ✅ useCurrentFrame() + interpolate/spring
- ❌ HTML <img>/<video> → ✅ Remotion <Img>/<Video>
- ❌ Hardcoded paths → ✅ staticFile()
- ❌ interpolate without clamp → ✅ Always add extrapolateLeft/Right: 'clamp'
---
## Constants-First Design Principle
> Source: remotion-dev/template-prompt-to-motion-graphics
All generated code MUST follow the Constants-First Design pattern:
1. **All editable values at the top** of each file as typed constants
2. **Grouped by concern**: BRAND (colors), TYPOGRAPHY (fonts/sizes), CONTENT (text), TIMING (frames/durations)
3. **Single source of truth**: No duplicated color/font/size values scattered in component code
4. **Type-safe**: Use TypeScript interfaces for brand and content configurations
This ensures generated videos can be quickly customized by editing only the constant block at the top, without understanding component internals.
---
## Skill Detection and Injection
> Source: remotion-dev/template-prompt-to-motion-graphics
When planning a video, analyze the requirements to determine which Remotion skill rules to reference:
| Video Need | Inject Rules From |
|------------|------------------|
| Text animations | `rules/text-animations.md` |
| Charts/graphs | `rules/charts.md` (if exists) |
| Scene transitions | `rules/transitions.md` |
| Spring physics | `rules/timing.md` |
| Image handling | `rules/images.md` |
| Audio sync | `rules/audio.md` (if exists) |
| 3D elements | `rules/three.md` (if exists) |
| Captions | `rules/display-captions.md`, `rules/import-srt-captions.md` |
Only inject relevant rules — avoid bloating context with unused skill content.
---
## Brand Configuration System
> Source: digitalsamba/claude-code-video-toolkit
When user provides brand information, structure it into a reusable brand config:
```typescript
const BRAND_CONFIG = {
colors: {
primary: '#[user-color]',
accent: '#[derived-or-specified]',
background: '#[dark-or-light]',
text: '#[contrast-to-bg]',
},
typography: {
heading: { font: '[user-font or Inter]', weight: 700, sizes: [72, 60, 48] },
body: { font: '[user-font or Inter]', weight: 400, sizes: [36, 28, 24] },
},
animation: {
style: 'smooth', // or 'snappy' or 'bouncy'
springConfig: { damping: 100, stiffness: 200 },
},
};
This config is embedded at the top of every generated component, ensuring brand consistency across all scenes.
This skill transforms vague video ideas into precise, implementable specifications that result in high-quality, professional videos. It leverages community-proven templates, the Constants-First Design principle, and structured polish rounds to consistently produce polished output.
1---
2name: scene-planner
3description: Creates detailed video storyboards and scene breakdowns for Remotion video generation. Analyzes user requirements, determines video type, selects appropriate template, and outputs structured scene plans with visual specifications, timing, animation details, and asset requirements. Use when planning video structure before code generation.
4metadata:
5 source: https://skillmd.com/skills/ahang1598/scene-planner
6---
7
8# Video Scene Planner
9
10You are responsible for transforming user video requirements into production-ready storyboards with precise specifications that the video-generator skill can implement with Remotion.
11
12## When This Skill Activates
13
14This skill activates automatically when:
15- The video-generator skill receives a video creation request
16- User explicitly requests storyboard or scene planning
17- Video structure needs to be revised based on feedback
18
19## Core Responsibilities
20
211. **Analyze user requirements** and extract video specifications
222. **Classify video type** (explainer, product demo, social media, presentation, product launch, open-source promo, data ranking, map route, kinetic typography, app walkthrough, before/after, thread summary, music visualization, release announcement)
233. **Select appropriate template** from the templates library
244. **Create scene breakdown** with timing and visual specifications
255. **Define design system** (colors, fonts, spacing, animations)
266. **List asset requirements** so user knows what to provide
277. **Output structured storyboard** ready for code generation
28
29---
30
31## Planning Process
32
33### Step 1: Requirements Analysis
34
35Extract the following from user input:
36
37#### Essential Information
38
39**Video purpose/goal**:
40- What is the video trying to achieve?
41- Examples: Explain concept, showcase product, drive signups, educate viewers
42
43**Target audience**:
44- Who will watch this video?
45- Examples: Developers, business executives, general consumers, students
46
47**Key messages**:
48- What are the 3-5 main points to communicate?
49- What should viewers remember after watching?
50
51**Duration preference**:
52- How long should the video be?
53- Default based on type if not specified:
54 - Explainer: 60-120 seconds
55 - Product demo: 45-75 seconds
56 - Social media: 15-30 seconds
57 - Presentation: 120-240 seconds
58
59#### Additional Context
60
61**Style preferences**:
62- Professional/corporate, creative/modern, minimal/clean, energetic/bold?
63- Any reference videos or styles mentioned?
64
65**Brand elements**:
66- Brand colors (hex codes if provided)
67- Logo availability
68- Fonts (if specified)
69
70**Available assets**:
71- Images, screenshots, product photos
72- Logo files
73- Background music or voiceover
74- Existing content (slides, documents, scripts)
75
76**Technical constraints**:
77- Aspect ratio (16:9 standard, 9:16 vertical, 1:1 square)
78- Resolution (1920x1080 default)
79- File size limitations
80- Platform requirements (Instagram, YouTube, etc.)
81
82#### If Information is Missing
83
84Ask clarifying questions (but be selective - don't overwhelm user):
85
86**Critical questions** (always ask if unclear):
87- "What's the main message or goal for this video?"
88- "How long should it be?"
89- "What visual assets do you have available (images, logos, etc.)?"
90
91**Optional questions** (ask only if relevant):
92- "Who is your target audience?"
93- "Any specific brand colors to use?"
94- "What style do you prefer: professional, creative, minimal, or bold?"
95
96**Smart defaults** (use if user doesn't specify):
97- Audience: Assume general/broad audience
98- Style: Professional and clean (works for most cases)
99- Colors: Use neutral palette (blacks, whites, grays with one accent color)
100
101---
102
103### Step 2: Video Type Classification
104
105Determine the primary video type based on requirements:
106
107#### Explainer Video
108**Indicators**:
109- User mentions: "explain", "educate", "how it works", "understand", "learn"
110- Goal is teaching a concept or process
111- Problem-solution structure mentioned
112
113**Characteristics**:
114- Duration: 60-180 seconds
115- Structure: Hook → Problem → Solution → How It Works → Benefits → CTA
116- Visual style: Clean, educational, icon-driven
117
118#### Product Demo
119**Indicators**:
120- User mentions: "showcase", "demo", "features", "product", "app", "platform"
121- Goal is showing software or product functionality
122- Screenshots or UI mentioned
123
124**Characteristics**:
125- Duration: 30-90 seconds
126- Structure: Intro → Overview → Feature Highlights → Value Prop → CTA
127- Visual style: Product-focused, annotation-heavy, professional
128
129#### Social Media
130**Indicators**:
131- User mentions: "Instagram", "TikTok", "Reels", "Shorts", "viral", "trending"
132- Goal is attention-grabbing and brief
133- Vertical format requested or implied
134
135**Characteristics**:
136- Duration: 15-60 seconds
137- Structure: Hook → Message → Visual → CTA
138- Visual style: Bold, high-contrast, fast-paced
139- Format: Often 9:16 (vertical)
140
141#### Presentation
142**Indicators**:
143- User mentions: "slides", "presentation", "deck", "pitch", "report"
144- Goal is structured information delivery
145- Multiple topics or sections mentioned
146
147**Characteristics**:
148- Duration: 120-300 seconds
149- Structure: Title → Content Slides → Summary → Closing
150- Visual style: Professional, slide-based, data-friendly
151
152#### Product Launch Announcement
153**Indicators**:
154- User mentions: "launch", "announce", "new product", "waitlist", "reveal"
155- Goal is creating buzz for a new product or major feature
156- Short, punchy format
157
158**Characteristics**:
159- Duration: 10-15 seconds
160- Structure: Hook → Selling Points → Before/After → CTA
161- Visual style: Minimalist, dark background, high contrast, typewriter effects
162- FPS: 60
163
164#### Open Source Project Promo
165**Indicators**:
166- User mentions: "open source", "GitHub", "npm", "library", "framework", "CLI", "stars"
167- Goal is attracting users/contributors to an OSS project
168- Developer-oriented aesthetic
169
170**Characteristics**:
171- Duration: 15-30 seconds
172- Structure: Project Identity → Features → Social Proof → Install CTA
173- Visual style: GitHub dark theme, terminal aesthetic, monospace fonts
174
175#### Data Ranking / Top N
176**Indicators**:
177- User mentions: "ranking", "top 10", "chart", "data", "comparison", "statistics", "leaderboard"
178- Goal is visualizing ranked or comparative data
179- Numerical data provided
180
181**Characteristics**:
182- Duration: 15-30 seconds
183- Structure: Title → Animated Bars → Insight Summary
184- Visual style: Clean, data-driven, animated bar charts
185
186#### Map Route / City Zoom
187**Indicators**:
188- User mentions: "map", "route", "locations", "journey", "cities", "travel", "offices"
189- Goal is showing geographical movement or location highlights
190- Multiple location points mentioned
191
192**Characteristics**:
193- Duration: 15-30 seconds
194- Structure: Map Overview → Route Animation → Location Highlights → Summary
195- Visual style: Dark themed map, SVG route drawing, zoom effects
196
197#### Kinetic Typography
198**Indicators**:
199- User mentions: "text animation", "quote", "lyrics", "words", "typography", "manifesto"
200- Goal is communicating through animated text as primary visual
201- Script or text-heavy content
202
203**Characteristics**:
204- Duration: 15-60 seconds
205- Structure: Sequential text with motion, scale, rotation, color
206- Visual style: Bold typography, minimal background, emphasis effects
207- FPS: 60
208
209#### App Walkthrough / UI Demo
210**Indicators**:
211- User mentions: "walkthrough", "UI", "screens", "app demo", "user flow", "tutorial"
212- Goal is guiding through app screens with device frame
213- Screenshots or screen recordings mentioned
214
215**Characteristics**:
216- Duration: 30-60 seconds
217- Structure: App Intro → Screen-by-Screen → Key Interaction → CTA
218- Visual style: Device mockup, spotlight highlights, captions
219
220#### Before/After Comparison
221**Indicators**:
222- User mentions: "before", "after", "comparison", "transformation", "improvement", "upgrade"
223- Goal is showing dramatic contrast between old and new states
224- Two-state data mentioned
225
226**Characteristics**:
227- Duration: 10-20 seconds
228- Structure: Context → Before State → Transition → After State → Summary
229- Visual style: Split screen, desaturated vs vibrant, red vs green
230
231#### Thread / Post Summary
232**Indicators**:
233- User mentions: "thread", "tweet", "summary", "key points", "newsletter", "carousel"
234- Goal is converting long-form text into visual video
235- Sequential points or numbered list provided
236
237**Characteristics**:
238- Duration: 20-45 seconds
239- Structure: Thread Title → Key Points Sequence → Takeaway → CTA
240- Visual style: Twitter/X dark theme, card-based, progress dots
241
242#### Music Visualization
243**Indicators**:
244- User mentions: "music", "audio", "visualization", "waveform", "spectrum", "podcast"
245- Goal is creating visual response to audio
246- Audio file provided or referenced
247
248**Characteristics**:
249- Duration: Matches audio length
250- Structure: Audio Analysis → Visual Response → Continuous Visualization
251- Visual style: Bars/circles/waves, gradient colors, glow effects
252- FPS: 60
253
254#### Release / Version Announcement
255**Indicators**:
256- User mentions: "release", "version", "update", "changelog", "v2", "v3", "patch"
257- Goal is announcing a software version update
258- Changelog items or feature list provided
259
260**Characteristics**:
261- Duration: 15-30 seconds
262- Structure: Version Badge → What's New List → Key Highlight → Upgrade CTA
263- Visual style: Dark, changelog-style, colored tags (NEW/IMPROVED/FIXED)
264
265**Multiple types**: If video crosses categories, choose primary type based on dominant goal.
266
267---
268
269### Step 3: Template Selection
270
271Load the appropriate template from `${CODEBUDDY_PLUGIN_ROOT}/templates/`:
272
273**Core Templates**:
274- **explainer-video.md**: For educational/explanatory content
275- **product-demo.md**: For software/product showcases
276- **social-media.md**: For short-form social content
277- **presentation.md**: For slide-based presentations
278
279**Extended Templates**:
280- **product-launch.md**: For product launch announcements (10-15s, 60fps)
281- **open-source-promo.md**: For open-source project promotion
282- **data-ranking.md**: For Top N / data ranking animations
283- **map-route.md**: For map route / city zoom animations
284- **kinetic-typography.md**: For text-as-visual kinetic typography (60fps)
285- **app-walkthrough.md**: For app UI walkthroughs with device frames
286- **before-after.md**: For before/after comparison videos
287- **thread-summary.md**: For Twitter/X thread summaries
288- **music-visualization.md**: For audio-reactive visualizations (60fps)
289- **release-announcement.md**: For software release/changelog announcements
290
291**How to use templates**:
2921. Read the template file for the selected video type
2932. Use its structure as the foundation
2943. Adapt to user's specific requirements
2954. Apply template guidelines (timing, layout, animation patterns)
296
297---
298
299### Step 4: Scene Breakdown
300
301Create a detailed scene-by-scene breakdown following this structure:
302
303#### Scene Specification Format
304
305For each scene, define:
306
307```json
308{
309 "scene_id": 1,
310 "name": "Hook",
311 "duration_seconds": 5,
312 "from_frame": 0,
313 "duration_frames": 150,
314 "type": "title|content|feature|transition|cta",
315
316 "content": {
317 "heading": "Scene heading text",
318 "body": "Main content text",
319 "typography": {
320 "heading_font": "Inter",
321 "heading_size": 60,
322 "heading_weight": 700,
323 "heading_color": "#1a1a1a",
324 "body_font": "Inter",
325 "body_size": 28,
326 "body_weight": 400,
327 "body_color": "#4a5568"
328 },
329 "layout": "centered|left-aligned|split-screen|full-bleed",
330 "background": {
331 "type": "solid|gradient|image",
332 "value": "#ffffff" or "linear-gradient(...)" or "asset-path.jpg"
333 }
334 },
335
336 "animations": [
337 {
338 "element": "heading|body|image|icon",
339 "type": "fade-in|slide-in|scale|spring|typewriter",
340 "start_frame": 0,
341 "duration_frames": 30,
342 "easing": "smooth|snappy|bouncy",
343 "config": {
344 "damping": 100,
345 "stiffness": 200
346 }
347 }
348 ],
349
350 "assets": [
351 {
352 "type": "image|video|icon|logo",
353 "name": "Descriptive asset name",
354 "path": "public/assets/filename.ext",
355 "position": "background|foreground|centered|top-right",
356 "size": "full|large|medium|small",
357 "fit": "cover|contain|fill",
358 "optional": false
359 }
360 ],
361
362 "transitions": {
363 "in": "fade|slide|wipe|none",
364 "out": "fade|slide|wipe|none",
365 "duration_frames": 20
366 }
367}
368```
369
370#### Scene Calculation
371
372**Frame rate**: Default to 30 fps
373- Alternative: 60 fps for ultra-smooth (mention if needed)
374
375**Frame calculation**:
376```
377duration_frames = duration_seconds * fps
378```
379
380Example: 5 seconds @ 30fps = 150 frames
381
382**Cumulative timing**:
383- Scene 1: from_frame = 0
384- Scene 2: from_frame = Scene 1 duration_frames
385- Scene 3: from_frame = Scene 1 + Scene 2 duration_frames
386- And so on...
387
388#### Scene Types
389
390**Title/Hook Scene**:
391- Purpose: Grab attention or introduce topic
392- Duration: 3-5 seconds
393- Visual: Centered text, bold typography, solid background
394- Animation: Fade in + slight scale
395
396**Content Scene**:
397- Purpose: Deliver main information
398- Duration: 10-15 seconds
399- Visual: Heading + body text or bullets
400- Animation: Sequential reveals
401
402**Feature Scene** (for demos):
403- Purpose: Highlight specific functionality
404- Duration: 10-12 seconds
405- Visual: Screenshot + annotation
406- Animation: Pan or spotlight effect
407
408**Transition Scene**:
409- Purpose: Bridge between major sections
410- Duration: 1-2 seconds
411- Visual: Minimal (often just animation)
412- Animation: Wipe, fade, or slide
413
414**CTA Scene**:
415- Purpose: Drive user action
416- Duration: 5-7 seconds
417- Visual: Bold CTA text + URL
418- Animation: Pulse or glow effect
419
420---
421
422### Step 5: Visual Design System
423
424Define a consistent visual language for the entire video:
425
426#### Color Palette
427
428Choose based on:
429- User-specified brand colors (if provided)
430- Video type and audience
431- Accessibility (ensure sufficient contrast)
432
433**Standard palette structure**:
434```json
435{
436 "primary": "#2563EB", // Main brand color
437 "secondary": "#7C3AED", // Complementary color
438 "accent": "#F97316", // Highlight/CTA color
439 "background": "#FFFFFF", // Main background
440 "background_alt": "#F3F4F6", // Alternate background
441 "text_primary": "#111827", // Main text color
442 "text_secondary": "#6B7280" // Secondary text
443}
444```
445
446**Color psychology**:
447- Blue: Trust, professionalism, tech
448- Green: Growth, health, eco
449- Purple: Creativity, luxury, innovation
450- Orange/Red: Energy, urgency, excitement
451- Black/White: Elegance, simplicity, clarity
452
453**Ensure accessibility**:
454- Contrast ratio 4.5:1 minimum for normal text
455- Contrast ratio 3:1 minimum for large text (18px+ bold or 24px+ regular)
456
457#### Typography
458
459**Font selection**:
460- Sans-serif for modern/digital content (Inter, Roboto, Poppins, Montserrat)
461- Serif for formal/traditional (Merriweather, Lora)
462- Monospace for technical content (Fira Code, JetBrains Mono)
463
464**Size hierarchy** (for 1920x1080):
465```json
466{
467 "hero": 72, // Main titles
468 "h1": 60, // Scene titles
469 "h2": 48, // Subtitles
470 "body_large": 36, // Emphasis text
471 "body": 28, // Standard text
472 "body_small": 24, // Secondary text
473 "caption": 18 // Fine print, footnotes
474}
475```
476
477**Weight scale**:
478- 400: Regular (body text)
479- 500: Medium (secondary headings)
480- 600: Semi-bold (subheadings)
481- 700: Bold (headings)
482- 800-900: Extra bold (hero text, impact)
483
484#### Spacing & Layout
485
486**Margins** (safe zones):
487- Standard 16:9: 80-100px from edges
488- Vertical 9:16: 60px sides, 80px top, 120px bottom
489- Square 1:1: 80px all sides
490
491**Padding** (between elements):
492- Between heading and body: 40-60px
493- Between paragraphs: 30-40px
494- Between list items: 20-30px
495
496**Grid system**:
497- Use 12-column grid for alignment
498- Consistent spacing multiples (8px, 16px, 24px, 32px, 40px, 48px)
499
500#### Animation Style
501
502**Easing presets** (for Remotion spring animations):
503
504**Smooth** (professional, subtle):
505```json
506{
507 "damping": 100,
508 "stiffness": 200
509}
510```
511
512**Snappy** (dynamic, responsive):
513```json
514{
515 "damping": 200,
516 "stiffness": 400
517}
518```
519
520**Bouncy** (playful, energetic):
521```json
522{
523 "damping": 50,
524 "stiffness": 300
525}
526```
527
528**Timing guidelines**:
529- Fade: 15-30 frames (0.5-1 second)
530- Slide: 20-40 frames (0.67-1.33 seconds)
531- Scale: 15-30 frames
532- Spring: Let physics determine (usually 30-60 frames)
533
534**Stagger timing** (sequential reveals):
535- Between list items: 15-30 frames apart
536- Between words: 5-10 frames apart
537- Between characters (typewriter): 2-3 frames apart
538
539---
540
541### Step 6: Technical Specifications
542
543#### Video Configuration
544
545```json
546{
547 "fps": 30,
548 "width": 1920,
549 "height": 1080,
550 "aspectRatio": "16:9",
551 "durationInFrames": 1800,
552 "durationInSeconds": 60,
553 "format": "mp4",
554 "codec": "h264",
555 "audioCodec": "aac"
556}
557```
558
559**Frame rate selection**:
560- 30 fps: Standard, efficient, works for most content
561- 60 fps: Ultra-smooth, for high-motion content, larger files
562
563**Resolution options**:
564- 1920x1080: Full HD, standard (default)
565- 3840x2160: 4K, premium quality, much larger files
566- 1080x1920: Vertical (social media)
567- 1080x1080: Square (Instagram feed)
568- 1280x720: HD, smaller files, acceptable quality
569
570**Audio** (if applicable):
571- Background music track
572- Voiceover narration
573- Sound effects
574
575---
576
577### Step 7: Asset Requirements
578
579Generate a comprehensive checklist of all assets needed:
580
581#### Essential Assets
582Mark as **required** - video cannot be generated without these:
583
584```markdown
585- [ ] Logo (PNG, transparent background, minimum 512x512px)
586- [ ] Product screenshot 1 (1920x1080 or higher)
587- [ ] Main visual/hero image (1920x1080 or higher)
588```
589
590#### Optional Assets
591Mark as **optional** - video can proceed without these but will be enhanced with them:
592
593```markdown
594- [ ] Background music (MP3/WAV, duration matching video length)
595- [ ] Additional product screenshots
596- [ ] Icon set (SVG or PNG, 64x64px each)
597- [ ] Custom fonts (if not using web fonts)
598```
599
600**Asset specifications**:
601- **Images**: PNG or JPG, RGB color mode, minimum 1920x1080 resolution
602- **Logos**: PNG with transparency, square aspect ratio, vector-based if possible
603- **Icons**: SVG (preferred) or PNG with transparency, 64x64px or larger
604- **Audio**: MP3 (256kbps) or WAV, length should match or exceed video duration
605- **Fonts**: TTF or OTF files, include all weights needed
606
607---
608
609## Output Format
610
611Generate a structured markdown storyboard document:
612
613```markdown
614# Video Storyboard: [Video Title]
615
616## Project Overview
617
618**Type**: [Explainer Video | Product Demo | Social Media | Presentation]
619**Duration**: [X] seconds ([Y] frames @ [Z] fps)
620**Resolution**: 1920x1080 (16:9)
621**Purpose**: [Brief description of video goal]
622**Target Audience**: [Who this is for]
623
624---
625
626## Design System
627
628### Color Palette
629- **Primary**: #2563EB (Blue - trust, professional)
630- **Secondary**: #7C3AED (Purple - creative)
631- **Accent**: #F97316 (Orange - CTA, attention)
632- **Background**: #FFFFFF (White)
633- **Text Primary**: #111827 (Near black)
634- **Text Secondary**: #6B7280 (Gray)
635
636### Typography
637- **Font Family**: Inter (sans-serif)
638- **Heading Sizes**: 72px (hero), 60px (h1), 48px (h2)
639- **Body Sizes**: 36px (large), 28px (standard), 24px (small)
640- **Weights**: 400 (regular), 600 (semi-bold), 700 (bold)
641
642### Animation Style
643- **Easing**: Smooth spring (damping: 100, stiffness: 200)
644- **Timing**: Fade 20 frames, Slide 30 frames
645- **Stagger**: 20 frames between sequential elements
646
647---
648
649## Scene Breakdown
650
651### Scene 1: Hook / Title Screen
652**Duration**: 5 seconds (0:00 - 0:05, frames 0-150)
653
654**Visual Description**:
655- Centered bold text on solid blue background
656- White typography, 72px
657- Clean, minimal composition
658
659**Content**:
660- Heading: "[Attention-grabbing question or statement]"
661- No body text
662
663**Animation**:
664- Frame 0-20: Fade in from 0% to 100% opacity
665- Frame 10-30: Scale from 0.95 to 1.0 (slight zoom)
666- Frame 120-150: Hold steady
667
668**Assets Required**:
669- Logo (top-right corner, 100x100px)
670
671**Transitions**:
672- In: Fade (20 frames)
673- Out: Fade (20 frames)
674
675---
676
677### Scene 2: [Next Scene Name]
678[Repeat structure for each scene...]
679
680---
681
682## Complete Timeline
683
684| Scene | Content | Duration | Frames | Cumulative Time |
685|-------|---------|----------|--------|-----------------|
686| 1 | Hook | 5s | 0-150 | 0:00-0:05 |
687| 2 | Problem | 12s | 150-510 | 0:05-0:17 |
688| 3 | Solution | 8s | 510-750 | 0:17-0:25 |
689| 4 | How It Works | 30s | 750-1650 | 0:25-0:55 |
690| 5 | CTA | 5s | 1650-1800 | 0:55-1:00 |
691| **Total** | | **60s** | **1800** | **0:00-1:00** |
692
693---
694
695## Asset Requirements
696
697### Essential (Required)
698- [ ] Logo (PNG, transparent, 512x512px minimum)
699- [ ] [Specific asset 1]
700- [ ] [Specific asset 2]
701
702### Optional (Recommended)
703- [ ] Background music (MP3, 60s, upbeat/neutral)
704- [ ] [Optional asset 1]
705- [ ] [Optional asset 2]
706
707### Asset Specifications
708- **Image Format**: PNG or JPG, RGB mode
709- **Minimum Resolution**: 1920x1080
710- **File Naming**: Use kebab-case (logo-main.png, screenshot-1.jpg)
711- **Asset Location**: Place in public/assets/ directory
712
713---
714
715## Technical Configuration
716
717```json
718{
719 "composition_name": "[video-name]",
720 "fps": 30,
721 "width": 1920,
722 "height": 1080,
723 "duration_frames": 1800,
724 "video_image_format": "jpeg",
725 "overwrite_output": true
726}
727```
728
729---
730
731## Notes & Considerations
732
733- [Any special notes about implementation]
734- [Platform-specific requirements]
735- [Accessibility considerations]
736- [Performance optimizations]
737
738---
739
740## Next Steps
741
7421. **Review storyboard**: Confirm structure and content
7432. **Gather assets**: Collect all required files
7443. **Generate code**: Proceed to Remotion implementation
7454. **Preview**: Use Remotion Studio to review
7465. **Render**: Generate final MP4 file
747```
748
749---
750
751## Best Practices
752
753### Content Planning
754
755**One idea per scene**: Don't try to communicate multiple concepts in one scene
756
757**Visual hierarchy**: Most important content should be most prominent
758
759**Pacing**: Allow enough time to read text (general rule: 3 seconds per sentence)
760
761**Consistency**: Maintain visual style throughout all scenes
762
763**Progressive disclosure**: Reveal information sequentially, not all at once
764
765### Timing Guidelines
766
767**Minimum scene duration**: 3 seconds (anything shorter feels rushed)
768
769**Maximum scene duration**: 20 seconds (unless it's complex data visualization)
770
771**Reading time**: Allow 2-3 seconds per line of text for viewers to read comfortably
772
773**Animation duration**: Keep transitions under 1 second (20-30 frames @ 30fps)
774
775**Pause between scenes**: Brief hold (30-60 frames) before transition
776
777### Animation Principles
778
779**Ease in**: Use for scene entrances (feels natural)
780
781**Ease out**: Use for scene exits (graceful departure)
782
783**Spring physics**: Use for interactive feel (buttons, icons)
784
785**Avoid motion sickness**: No rapid spinning, excessive shaking, or jarring movements
786
787**Purposeful movement**: Every animation should have a reason (reveal, emphasis, transition)
788
789### Accessibility
790
791**Color contrast**: Ensure text is readable (4.5:1 ratio minimum)
792
793**Font size**: Don't go below 24px for important text
794
795**Captions**: Include text on screen (many watch without sound)
796
797**Simple language**: Avoid jargon, use clear terminology
798
799**Visual clarity**: Don't overlay text on busy backgrounds
800
801---
802
803## Template Adaptation
804
805When adapting templates to user requirements:
806
807**Preserve structure**: Keep the proven scene flow from templates
808
809**Customize content**: Replace placeholder text with user's specific content
810
811**Adapt timing**: Adjust durations based on content complexity
812
813**Apply branding**: Use user's colors, fonts, and visual style
814
815**Respect best practices**: Follow template guidelines for timing and animation
816
817**Add personality**: Incorporate user's unique style while maintaining quality
818
819---
820
821## Example Workflow
822
823**User Request**: "I need a 60-second explainer video about our task management app"
824
825**Planning Process**:
826
8271. **Analyze requirements**:
828 - Purpose: Explain task management app
829 - Type: Explainer video
830 - Duration: 60 seconds
831 - Audience: Productivity-focused users
832
8332. **Load template**: explainer-video.md
834
8353. **Scene breakdown** (based on template):
836 - Scene 1: Hook (4s) - "Drowning in tasks?"
837 - Scene 2: Problem (12s) - Scattered tasks, missed deadlines
838 - Scene 3: Solution (8s) - Introduce app
839 - Scene 4: How It Works (26s) - 3 key features
840 - Scene 5: Benefits (7s) - Time saved, clarity
841 - Scene 6: CTA (3s) - "Try free at [website]"
842
8434. **Define design**:
844 - Colors: Blue (trust, productivity), White (clean)
845 - Fonts: Inter (modern, readable)
846 - Animation: Smooth spring (professional feel)
847
8485. **List assets**:
849 - App logo
850 - 3 feature screenshots
851 - App icon
852
8536. **Output storyboard**: Complete markdown document as specified above
854
855**Total planning time**: 2-3 minutes
856
857---
858
859## Integration with Other Skills
860
861### Called by video-generator
862
863The video-generator skill invokes this skill to plan video structure before generating Remotion code.
864
865### Uses templates
866
867This skill reads template files from `${CODEBUDDY_PLUGIN_ROOT}/templates/` directory.
868
869### Output to video-generator
870
871Returns complete storyboard specification that video-generator uses to:
872- Generate Remotion React components
873- Create scene-specific files
874- Configure composition timing
875- Set up asset references
876
877---
878
879## Extended Video Type Classification
880
881Beyond the 4 core types (explainer, product demo, social media, presentation), this skill also supports these high-impact video styles from the prompt library:
882
883### Product Launch / Feature Announcement
884**Indicators**: "launch", "announce", "release", "new feature", "공告"
885**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/01-product-launch.md`
886**Characteristics**: 10-15s, dark background, high contrast, typewriter + blur effects
887
888### Developer Tool Promo
889**Indicators**: "open source", "CLI", "SDK", "developer tool", "npm", "GitHub"
890**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/02-developer-tool-promo.md`
891**Characteristics**: 12-18s, terminal-style cards, command typing, counter animations
892
893### Data Ranking / Top N
894**Indicators**: "ranking", "top 10", "leaderboard", "chart", "data", "statistics"
895**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/03-data-ranking.md`
896**Characteristics**: 15-30s, animated bar charts, count-up numbers, staggered reveals
897
898### Kinetic Typography
899**Indicators**: "quote", "lyrics", "金句", "caption", "口播", "typography"
900**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/04-kinetic-typography.md`
901**Characteristics**: 8-15s, word-by-word reveals, highlight emphasis, gradient backgrounds
902
903### App Walkthrough
904**Indicators**: "walkthrough", "tutorial", "step by step", "how to use", "UI demo"
905**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/05-app-walkthrough.md`
906**Characteristics**: 15-25s, phone frame, highlight boxes, info bubbles
907
908### Before vs After
909**Indicators**: "before after", "comparison", "对比", "vs", "versus"
910**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/06-before-after.md`
911**Characteristics**: 10-15s, split screen, staggered reveals, breathing divider
912
913### Release Announcement
914**Indicators**: "changelog", "version", "update", "release notes", "v2.0"
915**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/07-release-announcement.md`
916**Characteristics**: 8-12s, version badge, typewriter, blur-in effects
917
918### Thread / Post Summary
919**Indicators**: "thread", "summary", "帖子", "list", "要点", "takeaways"
920**Template**: `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/08-thread-summary.md`
921**Characteristics**: 15-25s, card-based, news-style header, numbered points
922
923---
924
925## Post-Generation Polish Process
926
927After the initial storyboard and code generation, apply a structured polish process to elevate quality from "functional" to "professional". Reference the polish prompts at `${CODEBUDDY_PLUGIN_ROOT}/templates/prompt-library/09-polish-prompts.md`.
928
929### Polish Round 1: Structure Check
930- Verify content is correct and complete
931- Check timeline is logical (hook fast → content steady → CTA clear)
932- Ensure every scene has enough reading time (2-3s per line)
933- Add "hold" periods after key information (30-60 frames)
934
935### Polish Round 2: Visual Consistency
936- Unify to maximum 2 fonts (heading + body)
937- Limit to 1 primary + 1 accent color (rest is grayscale)
938- Align all spacing to 8px grid
939- Verify contrast ratios (4.5:1 for text, 3:1 for large text)
940- Check: no pure black (#000) or pure white (#FFF) — use near-black and near-white
941
942### Polish Round 3: Animation Refinement
943- Replace linear animations with spring() where appropriate
944- Add clamp to all interpolate() calls
945- Apply subtle background motion (gradient drift, noise float, breathing scale)
946- Ensure text reveals are staggered (not everything at once)
947- Scene exits should be 30% faster than entrances
948- All transitions use crossfade + subtle blur (15-25 frames)
949
950### Polish Round 4: Detail Enhancement
951- Add box-shadow for depth (cards, panels)
952- Check safe zones (80px from edges for 16:9, 60px sides + 80px top/120px bottom for 9:16)
953- Verify text line width doesn't exceed 60 chars (EN) or 30 chars (ZH)
954- Add subtle glow effects on CTA elements
955
956### Anti-Pattern Checklist
957During polish, verify these common mistakes are avoided:
958
959- ❌ Per-character opacity for typewriter → ✅ Use string.slice()
960- ❌ Abrupt cursor blink → ✅ Smooth interpolated blink
961- ❌ No fixed width on word carousel → ✅ Measure longest word
962- ❌ CSS transition/animation → ✅ useCurrentFrame() + interpolate/spring
963- ❌ HTML <img>/<video> → ✅ Remotion <Img>/<Video>
964- ❌ Hardcoded paths → ✅ staticFile()
965- ❌ interpolate without clamp → ✅ Always add extrapolateLeft/Right: 'clamp'
966
967---
968
969## Constants-First Design Principle
970
971> Source: remotion-dev/template-prompt-to-motion-graphics
972
973All generated code MUST follow the Constants-First Design pattern:
974
9751. **All editable values at the top** of each file as typed constants
9762. **Grouped by concern**: BRAND (colors), TYPOGRAPHY (fonts/sizes), CONTENT (text), TIMING (frames/durations)
9773. **Single source of truth**: No duplicated color/font/size values scattered in component code
9784. **Type-safe**: Use TypeScript interfaces for brand and content configurations
979
980This ensures generated videos can be quickly customized by editing only the constant block at the top, without understanding component internals.
981
982---
983
984## Skill Detection and Injection
985
986> Source: remotion-dev/template-prompt-to-motion-graphics
987
988When planning a video, analyze the requirements to determine which Remotion skill rules to reference:
989
990| Video Need | Inject Rules From |
991|------------|------------------|
992| Text animations | `rules/text-animations.md` |
993| Charts/graphs | `rules/charts.md` (if exists) |
994| Scene transitions | `rules/transitions.md` |
995| Spring physics | `rules/timing.md` |
996| Image handling | `rules/images.md` |
997| Audio sync | `rules/audio.md` (if exists) |
998| 3D elements | `rules/three.md` (if exists) |
999| Captions | `rules/display-captions.md`, `rules/import-srt-captions.md` |
1000
1001Only inject relevant rules — avoid bloating context with unused skill content.
1002
1003---
1004
1005## Brand Configuration System
1006
1007> Source: digitalsamba/claude-code-video-toolkit
1008
1009When user provides brand information, structure it into a reusable brand config:
1010
1011```typescript
1012const BRAND_CONFIG = {
1013 colors: {
1014 primary: '#[user-color]',
1015 accent: '#[derived-or-specified]',
1016 background: '#[dark-or-light]',
1017 text: '#[contrast-to-bg]',
1018 },
1019 typography: {
1020 heading: { font: '[user-font or Inter]', weight: 700, sizes: [72, 60, 48] },
1021 body: { font: '[user-font or Inter]', weight: 400, sizes: [36, 28, 24] },
1022 },
1023 animation: {
1024 style: 'smooth', // or 'snappy' or 'bouncy'
1025 springConfig: { damping: 100, stiffness: 200 },
1026 },
1027};
1028```
1029
1030This config is embedded at the top of every generated component, ensuring brand consistency across all scenes.
1031
1032---
1033
1034This skill transforms vague video ideas into precise, implementable specifications that result in high-quality, professional videos. It leverages community-proven templates, the Constants-First Design principle, and structured polish rounds to consistently produce polished output.