Convert notes/documents/SRT into a 9:16 short-form video. An agent team performs planning→production→review.
Production pipeline
입력 분석 → 기획팀(3인 병렬) → GIF 수집 → 제작팀(병렬) → TTS 생성 → 검수팀(병렬) → 렌더링
Step 1: Input analysis
Read and understand notes/URLs/text/SRT:
- Topic and target audience
- 3-5 messages to convey
- Story structure (problem→solution, concept→application, storytelling, etc.)
- Check if there are user images (characters, logos, screenshots, etc.)
Step 2: Dispatch planning team (3 people in parallel)
3개 Agent를 Simultaneously from one message call. model: "sonnet" specify.
Agent 1 — Planner: 6-scene layout zone map (Y-coordinate based), GIF placement area, animation timing Agent 2 — Copy/GIF Curator: GIF keyword selection (2-3 English words), medium-medium-medium-weak-strong rhythm Agent 3 — Reviewer: Analyze issues in existing code, suggest improvements
6-scene structure
| 씬 | Role | Recommended duration | GIF rhythm |
|---|---|---|---|
| 1 | 훅 | 8초 | None or medium |
| 2 | Context/background | 8-11초 | 중 |
| 3 | Key concept | 9-10초 | 중 |
| 4 | Visualization/metaphor | 8-10초 | 중 or 약 |
| 5 | Comparison/deep dive | 10초 | 약 |
| 6 | Closing/CTA | 8-10초 | 강 |
GIF placement pattern (card news method)
GIF는 Scene top dedicated zone(top 35-50%) placed full-width. Never shares the same area as text.
┌─────────────────┐
│ GIF (full-width)│ ← 상단 35-50%
│ + gradient │ ← linear-gradient(to bottom, transparent 40%, bg 100%)
│ + 키워드 오버레이│
├─────────────────┤
│ 텍스트 콘텐츠 │ ← 하단 50-65%
│ (카드/차트 등) │
└─────────────────┘
- GIF opacity: 1.0 (do not apply translucency)
- gradient overlay required
- Overlay keyword on top of GIF (ensure readability with textShadow)
- Top zone of scenes without GIF: utilize as typography or image or 3D background
GIF search (gifgrep)
gifgrep "영어 키워드" --max 1 --format url --quiet 2>/dev/null
Keyword pattern: references/voiceover-workflow.md Refer to. If results are unsuitable, re-search with alternative keywords.
Step 3: Project setup
bash scripts/init-project.sh <project-dir>
Step 4: Select design style + write scene code
Design style options
| Style | Characteristics | Suitable topics |
|---|---|---|
| Dark neon | #0a0a0f background, cyan/purple accents, default | Technical explainers in general |
| Aurora Glassmorphism | breathing gradient background, glass panel, Radar Rings | Premium tech introduction |
| Launch video | Mac AppWindow chrome, amber accent, 3D perspective, converging lines | Product launches, tool introductions |
Common components
Use as needed in scenes:
- Highlight — rough.js-style highlighter marker (left→right expansion, keyword emphasis)
- ScannerLine — top→bottom scanning horizontal line (technical feel)
- CornerBrackets — 4 corner bracket decoration
- GlassPanel — Glassmorphism panel (backdrop-filter blur)
- AuroraBackground — breathing radial gradient background
- RadarRings — rotating dashed circle (radar feel)
- FloatingOrbs — floating glass spheres (depth-of-field blur)
Mac AppWindow pattern (launch video style)
Wrap all content in a Mac window chrome:
- traffic lights (red/yellow/green 14px circles)
- surface background + border
- content area: padding 24px 32px
Image insertion pattern
If the user provided an image:
public/images/copy to<Img src={staticFile("images/파일명")} />- spring explosive entrance (scale 0→1.15→1, damping 8)
- continuous floating (Math.sin-based y wobble)
- optional glitch effect (skewX when frame % 90 < 2)
- place a rotating dashed tech ring behind
Chart pattern
- Bar chart: bar height grows with spring, glow boxShadow
- Line chart: SVG strokeDasharray/offset로 progressive draw, pulsing dot
Required rules
- Frame-based animation only —
useCurrentFrame()+interpolate()/spring() - CSS transition/animation prohibited
- Deterministic rendering —
Math.random()prohibited,Math.sin(frame * N)use - Use COLORS constants — hardcoded colors prohibited
- Import fonts from fonts.ts
- position absolute + top-based (avoid using bottom)
- WebGL/ThreeCanvas prohibited — WebGL context errors during headless rendering. Replace with CSS 3D
- GIF는
<Gif>use component (@remotion/gif) —<Img>inserting a GIF causes jitter/stutter
Scene pattern details: references/scene-patterns.md
Step 5: Dispatch production team (2-3 parallel)
Split the 6 scenes among 2-3 Agents and write in parallel. Pass to each Agent:
- Planning team results (layout zone map, GIF URL, keywords)
- Design style + COLORS constants
- Common component list
- GIF/image paths
- Required rules
Step 6: Write script + generate TTS
Support 2 TTS engines:
| Engine | Condition | Command |
|---|---|---|
| ElevenLabs | When API key is present | npx tsx --env-file=.env scripts/generate-voiceover.ts config.json |
| Qwen TTS | When API key is absent (free) | npx tsx scripts/generate-voiceover-qwen.ts config.json |
Qwen TTS는 HuggingFace Qwen/Qwen3-TTS Use Space. Dylan voice, Korean support, no API key required.
Script writing
voiceover-config.jsonWrite with . Rules:
- Colloquial, 1-3 sentences per scene
- Avoid clichés ("innovative", "paradigm")
- Transliterate English/numbers into Korean as pronounced (e.g., AI→에이아이, Claude Code→클로드 코드)
- On-screen text stays in English, transliterate only in the script
Detailed transliteration rules: references/voiceover-workflow.md
TTS generation + audio integration
# ElevenLabs (API 키 필요)
npx tsx --env-file=.env scripts/generate-voiceover.ts voiceover-config.json
# Qwen TTS (무료, API 키 불필요)
npx tsx scripts/generate-voiceover-qwen.ts voiceover-config.json
Measure audio length → reset SCENE_DURATIONS in styles to audio + 1 second of margin.
For each scene, <Audio src={staticFile("voiceover/ID/scene-0X.mp3")} /> insert.
Adjust audio gaps after rendering
After checking the rendering result, if any scene has a large gap between voices:
ffprobeRe-measure audio length for each scene- SCENE_DURATIONS for scenes with large gaps to
오디오 길이 + 0.5초reduce to - Re-render
Step 7: Dispatch inspection team (3 teams in parallel)
3개 Agent를 simultaneously call:
- Code quality — TS errors, Remotion pattern compliance, no use of Math.random/CSS transition/useFrame
- Design consistency — 1080×1920 layout, no GIF zone overlap, typography hierarchy
- Motion timing — completion within animation scene, audio timing synchronization, dwell time
Checklist: references/review-checklist.md
If Critical is found, fix and re-inspect. Proceed with rendering after receiving PASS.
Step 8: Rendering
npx remotion render <CompositionId> out/<filename>.mp4 --codec h264
If there is a scene using WebGL, --concurrency 1 add.
Precautions
.envFiles must not be committed/uploaded (contains API keys)- GIF URLs are Tenor CDN links; local storage recommended for long-term preservation
- When loading NotoSansKR font,
ignoreTooManyRequestsWarning: truesetting