remotion-spec-translator
Orchestrates translation of motion designer video specifications into working Remotion code by coordinating specialized agents. Acts as pipeline coordinator that delegates to remotion-scaffold, remotion-animation, remotion-composition, and remotion-component-gen. Use when you have a complete VIDEO_SPEC.md and need full Remotion implementation.
What this skill does
# Remotion Spec Translator
Orchestrates the complete translation pipeline from motion design specifications to working Remotion code. This skill acts as a coordinator that delegates work to specialized skills for each aspect of the translation.
## What This Skill Does
Orchestrates the translation by:
1. **Coordinating pipeline** — Calls specialized skills in correct order
2. **Parsing specs** — Extracts requirements for each skill
3. **Managing handoffs** — Ensures output from one skill feeds into next
4. **Validating completeness** — Confirms all scenes implemented
5. **Documenting workflow** — Tracks pipeline progress
## Scope Boundaries
**IN SCOPE:**
- Pipeline orchestration and coordination
- Spec parsing and requirement extraction
- Skill delegation and sequencing
- Progress tracking and validation
- Workflow documentation
**OUT OF SCOPE:**
- Direct code generation (delegated to specialist skills)
- Implementation details (handled by component/animation skills)
- Manual file creation (handled by scaffold skill)
## Input/Output Formats
### Input Format: VIDEO_SPEC.md
Expects complete motion design specification (from `/motion-designer`):
```markdown
# Video Title: ProductDemo
## Overview
- Duration: 30 seconds
- Frame Rate: 30 fps
- Aspect Ratio: 16:9 (1920x1080)
- Total Scenes: 4
## Color Palette
Primary: #FF6B35 - Ember Orange
Secondary: #4ECDC4 - Teal
Background: #0A0A0A - Black
Text: #FFFFFF - White
## Scene 1: Intro (0s - 5s)
Visual Description: Centered logo with smooth entrance
Animation Details:
- Logo: Scale 0.8 → 1.0, Spring (damping: 200)
- Subtitle: Fade in with upward slide
## Scene 2: Features (5s - 15s)
Visual Description: Three feature cards stagger in
Animation Details:
- Cards: Stagger delay 10 frames, slide from left
## Scene 3: Demo (15s - 25s)
Visual Description: Product screenshot with highlights
Animation Details:
- Screenshot: Fade in, scale 0.95 → 1.0
- Highlights: Sequential pulse effect
## Scene 4: CTA (25s - 30s)
Visual Description: Call-to-action with button
Animation Details:
- Text: Fade in
- Button: Scale bounce effect
## Assets
- Logo: public/images/logo.svg (400x400)
- Product screenshot: public/images/product.png (1200x800)
```
### Output Format: TRANSLATION_COMPLETE.md
Generates orchestration summary document:
```markdown
# Translation Complete: ProductDemo
## Status
✅ Pipeline execution complete
✅ All scenes implemented
⏳ Ready for render
## Pipeline Execution Summary
### Step 1: Scaffold Generation (/remotion-scaffold)
✅ Complete
- Created: Project structure
- Output: SCAFFOLD_MANIFEST.md
- Files: index.tsx, constants.ts, types.ts, 4 scene templates
### Step 2: Animation Configuration (/remotion-animation)
✅ Complete
- Created: Animation parameters
- Output: ANIMATION_CONFIG.md
- Configs: Spring settings, interpolations, timing
### Step 3: Composition Structure (/remotion-composition)
✅ Complete
- Created: Sequence layout
- Output: COMPOSITION_STRUCTURE.md
- Timing: All scene durations calculated
### Step 4: Scene Implementation (/remotion-component-gen)
✅ Complete - 4/4 scenes
- Scene 1 (Intro): SCENE_COMPONENT.md → Scene1Intro.tsx
- Scene 2 (Features): SCENE_COMPONENT.md → Scene2Features.tsx
- Scene 3 (Demo): SCENE_COMPONENT.md → Scene3Demo.tsx
- Scene 4 (CTA): SCENE_COMPONENT.md → Scene4CTA.tsx
### Step 5: Render Configuration (/remotion-render-config)
✅ Complete
- Created: Render settings
- Output: RENDER_CONFIG.md
- Target: YouTube (H.264, CRF 18)
## Generated Files
```
src/remotion/compositions/ProductDemo/
├── index.tsx # ✅ Composition with all scenes
├── constants.ts # ✅ Colors, springs, timing
├── types.ts # ✅ TypeScript interfaces
└── scenes/
├── Scene1Intro.tsx # ✅ Implemented
├── Scene2Features.tsx # ✅ Implemented
├── Scene3Demo.tsx # ✅ Implemented
└── Scene4CTA.tsx # ✅ Implemented
```
## Next Steps
1. **Add assets** to public/ folders
- Logo: public/images/logo.svg
- Product screenshot: public/images/product.png
2. **Test in preview**
```bash
npm run dev
```
3. **Verify timing** matches spec exactly
4. **Run render** when ready
```bash
npm run render:youtube
```
5. **Review and iterate** if adjustments needed
## Asset Checklist
Required assets from spec:
- [ ] public/images/logo.svg (400x400)
- [ ] public/images/product.png (1200x800)
Use `/remotion-asset-coordinator` for asset sourcing guidance.
## Quality Checklist
- [x] All scenes implemented
- [x] Timing matches spec
- [x] Animations configured
- [x] Colors from palette applied
- [x] Composition structure complete
- [ ] Assets added
- [ ] Preview tested
- [ ] Final render complete
## Translation Summary
**Input:** VIDEO_SPEC.md (motion design specification)
**Pipeline:** 5 specialized skills executed in sequence
**Output:** Complete, working Remotion composition
**Status:** Implementation complete, assets and testing pending
```
## Orchestration Workflow
The pipeline executes in this sequence:
```
VIDEO_SPEC.md (Input)
↓
Step 1: /remotion-scaffold
↓ outputs: SCAFFOLD_MANIFEST.md + folder structure
Step 2: /remotion-animation
↓ outputs: ANIMATION_CONFIG.md + animation constants
Step 3: /remotion-composition
↓ outputs: COMPOSITION_STRUCTURE.md + Sequence layout
Step 4: /remotion-component-gen (per scene)
↓ outputs: SCENE_COMPONENT.md × N scenes
Step 5: /remotion-render-config
↓ outputs: RENDER_CONFIG.md + render commands
↓
TRANSLATION_COMPLETE.md (Output)
```
## Skill Delegation Strategy
### When to Delegate
1. **Parse spec** → Extract requirements for each skill
2. **Check dependencies** → Ensure prerequisites met
3. **Call skill** → Provide focused input
4. **Capture output** → Store for next skill
5. **Validate** → Confirm output quality
6. **Proceed** → Move to next step
### Delegation Examples
```typescript
// Step 1: Scaffold
const scaffoldInput = {
projectName: "ProductDemo",
duration: 30,
fps: 30,
dimensions: "1920x1080",
scenes: ["Intro", "Features", "Demo", "CTA"]
};
// Call: /remotion-scaffold
// Step 2: Animation
const animationInput = {
springConfigs: extractSpringConfigs(spec),
interpolations: extractInterpolations(spec),
timing: extractAnimationTiming(spec)
};
// Call: /remotion-animation
// Step 3: Composition
const compositionInput = {
scenes: [
{ name: "intro", durationSeconds: 5 },
{ name: "features", durationSeconds: 10 },
{ name: "demo", durationSeconds: 10 },
{ name: "cta", durationSeconds: 5 }
],
fps: 30
};
// Call: /remotion-composition
// Step 4: Component Gen (per scene)
for (const scene of spec.scenes) {
const componentInput = {
sceneName: scene.name,
visualDescription: scene.visual,
animationDetails: scene.animation,
assets: scene.assets
};
// Call: /remotion-component-gen
}
// Step 5: Render Config
const renderInput = {
platform: "YouTube",
quality: "high",
format: "MP4"
};
// Call: /remotion-render-config
```
## Spec Parsing Helpers
### Extract Spring Configs
```typescript
function extractSpringConfigs(spec: string) {
// Parse animation details for spring parameters
// Look for: damping, stiffness, mass values
// Return: SPRING_CONFIGS object
}
```
### Extract Scene Timing
```typescript
function extractSceneTiming(spec: string) {
// Parse scene headers for timing (0s - 5s)
// Calculate frame numbers
// Return: Scene timing array
}
```
### Extract Color Palette
```typescript
function extractColorPalette(spec: string) {
// Parse Color Palette section
// Extract hex codes and names
// Return: COLORS object
}
```
### Extract Asset List
```typescript
function extractAssets(spec: string) {
// Parse Assets sections per scene
// Collect all required assets
// Return: Asset checklist
}
```
## Progress Tracking
The orchestrator tracks pipeline progress:
```
Pipeline Progress: ProductDemo
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ SRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.