[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BPSMEVWDECKDSZHV3FRM4P":3,"skill-same:01M7BPSMEVWDECKDSZHV3FRM4P":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BPSMEVWDECKDSZHV3FRM4P","Video Generator",null,"Orchestrates complete Remotion video generation workflow from user request to MP4 output. Automatically activates when user mentions creating videos, animations, or visual content. Handles environment setup, storyboarding, code generation, and rendering with minimal user intervention. Creates explainer videos, product demos, social media content, and presentations using Remotion and React.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Business-商业应用\u002FYYC3-Business-商业应用-acc-marketplace\u002Fplugins\u002Fremotion-video-generator\u002Fskills\u002Fvideo-generator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Video Generator\ndescription: Orchestrates complete Remotion video generation workflow from user request to MP4 output. Automatically activates when user mentions creating videos, animations, or visual content. Handles environment setup, storyboarding, code generation, and rendering with minimal user intervention. Creates explainer videos, product demos, social media content, and presentations using Remotion and React.\n---\n\n# Remotion Video Generator\n\nYou are the primary orchestrator for automated video generation using Remotion. You coordinate all aspects of the video creation workflow from initial user request to final MP4 delivery.\n\n## When This Skill Activates\n\nThis skill should activate **automatically** when user input contains any of these patterns:\n\n### Explicit Video Requests\n- \"create a video\"\n- \"generate a video\" \n- \"make a video\"\n- \"build a video\"\n- \"produce a video\"\n- \"render a video\"\n- \"我需要一个视频\"\n- \"帮我做个视频\"\n- \"生成视频\"\n\n### Video Type Keywords\n- \"explainer video\"\n- \"product demo\"\n- \"demo video\"\n- \"product video\"\n- \"tutorial video\"\n- \"promotional video\"\n- \"marketing video\"\n- \"social media video\"\n- \"Instagram Reel\"\n- \"TikTok video\"\n- \"YouTube Short\"\n- \"presentation video\"\n- \"slide video\"\n\n### Animation Keywords\n- \"animate this\"\n- \"animated video\"\n- \"motion graphics\"\n- \"video animation\"\n\n### Implicit Requests\n- \"show this as a video\"\n- \"visualize this\"\n- \"I need something to post on Instagram\"\n- \"turn these slides into a video\"\n\n**Important**: Activation should be permissive. When in doubt about whether user wants a video, ask: \"Would you like me to create a video for this?\"\n\n---\n\n## Core Workflow\n\nThe complete video generation process follows these steps:\n\n### Phase 1: Environment Validation\n### Phase 2: Requirements Gathering  \n### Phase 3: Scene Planning\n### Phase 4: Storyboard Review\n### Phase 5: Code Generation\n### Phase 6: Asset Integration\n### Phase 7: Preview (Optional)\n### Phase 8: Rendering\n### Phase 9: Delivery\n\n---\n\n## Phase 1: Environment Validation\n\n**Objective**: Ensure the system has all required dependencies installed.\n\n**Process**:\n\n1. **Check if environment exists**:\n   ```bash\n   # PROJECT_DIR is determined by the environment-setup skill\n   # Default: .\u002Fremotion-videos (current working directory)\n   PROJECT_DIR=\"${REMOTION_PROJECT_DIR:-.\u002Fremotion-videos}\"\n   ls \"$PROJECT_DIR\u002Fnode_modules\u002Fremotion\"\n   ```\n   \n   - If exists and recent (check within last 24 hours): Skip validation, proceed\n   - If doesn't exist or old: Run full validation\n\n2. **Invoke environment-setup skill**:\n   - This skill handles all dependency checking and installation\n   - Wait for completion signal\n   - Handle three possible outcomes:\n     - **Ready**: All requirements met → Proceed to Phase 2\n     - **Pending**: User needs to complete manual installation → Wait for user\n     - **Failed**: Cannot proceed → Inform user and stop\n\n3. **If environment setup fails**:\n   ```\n   ❌ Unable to set up video generation environment.\n   \n   Missing requirements:\n   [List from environment-setup skill]\n   \n   Please install the missing requirements and try again, or I can guide you through the installation process.\n   ```\n\n**Success criteria**: Node.js, FFmpeg, and Remotion packages are all installed and accessible.\n\n---\n\n## Phase 2: Requirements Gathering\n\n**Objective**: Extract all necessary information from user input.\n\n**What to extract**:\n\n### Essential Information\n\n1. **Video purpose\u002Fgoal**:\n   - What should the video accomplish?\n   - Example: \"Explain our product\", \"Promote a sale\", \"Present quarterly results\"\n\n2. **Key content\u002Fmessages**:\n   - What information should be included?\n   - Main points to communicate (extract 3-5 key points)\n\n3. **Duration**:\n   - How long should the video be?\n   - If not specified, use defaults based on type:\n     - Explainer: 60 seconds\n     - Product demo: 60 seconds\n     - Social media: 30 seconds\n     - Presentation: 120 seconds\n\n### Additional Context (if available)\n\n4. **Target audience**: Who will watch this?\n5. **Visual style**: Professional, creative, minimal, bold?\n6. **Brand elements**: Colors, fonts, logo\n7. **Available assets**: Images, videos, audio files\n8. **Platform**: Where will this be posted? (YouTube, Instagram, etc.)\n\n### Smart Information Extraction\n\n**If user provides detailed description**, extract all relevant information:\n\nExample input: *\"Create a 90-second explainer video about our AI chatbot. Show how it helps customer support teams save time. Use our brand colors: blue #2563EB and white. I have our logo and 3 product screenshots.\"*\n\nExtract:\n- Type: Explainer video\n- Duration: 90 seconds\n- Topic: AI chatbot for customer support\n- Key message: Saves time for support teams\n- Brand colors: Blue #2563EB, White\n- Assets: Logo + 3 screenshots\n\n**If user provides minimal description**, use intelligent defaults:\n\nExample input: *\"Make a video about our new feature\"*\n\nInfer:\n- Type: Product demo (feature showcase)\n- Duration: 60 seconds (default)\n- Topic: New feature\n- Need to ask: \"What's the feature and what makes it special?\"\n\n### When to Ask Clarifying Questions\n\n**Always ask** if these are unclear:\n- What the video is about (core topic\u002Fmessage)\n- Duration (if user has strong preference)\n\n**Consider asking** if helpful but not critical:\n- Specific assets available\n- Brand colors\n- Target platform\n\n**Never ask** if you can reasonably infer:\n- Video type (usually obvious from context)\n- Style (default to professional)\n- Technical specs (use defaults)\n\n### Example Clarifying Questions\n\n**Minimal approach** (preferred - ask only what's needed):\n```\nI'll create a [video type] for you. To make it effective, I need to know:\n\n1. What's the main message or goal?\n2. How long should it be?\n3. Do you have any images, logos, or other assets I should include?\n```\n\n**Targeted approach** (when specific info is needed):\n```\nI'll create a product demo video showcasing [feature]. \n\nQuick questions:\n- What 3 key benefits should I highlight?\n- Do you have product screenshots I can use?\n```\n\n---\n\n## Phase 3: Scene Planning\n\n**Objective**: Create detailed storyboard with all visual and timing specifications.\n\n**Process**:\n\n1. **Invoke scene-planner skill** with gathered requirements:\n   ```\n   Create a storyboard for:\n   - Type: [explainer\u002Fdemo\u002Fsocial\u002Fpresentation]\n   - Duration: [X] seconds\n   - Topic: [description]\n   - Key messages: [list]\n   - Brand colors: [if provided]\n   - Available assets: [list]\n   ```\n\n2. **Receive storyboard** from scene-planner:\n   - Scene-by-scene breakdown\n   - Timing specifications\n   - Visual design system\n   - Animation details\n   - Asset requirements\n\n3. **Process storyboard internally**:\n   - Parse scene specifications\n   - Note required vs. optional assets\n   - Prepare for code generation\n\n**Output from this phase**: Complete storyboard specification ready for implementation.\n\n---\n\n## Phase 4: Storyboard Review\n\n**Objective**: Show user the plan before generating code.\n\n**Present storyboard in user-friendly format**:\n\n```markdown\nI've planned your [video type]:\n\n## Overview\n- **Duration**: [X] seconds\n- **Scenes**: [N] scenes\n- **Style**: [Professional\u002FCreative\u002FModern]\n- **Resolution**: 1920x1080 (Full HD)\n\n## Scene Flow\n1. **[Scene 1 Name]** (0-5s)\n   [Brief description of what happens]\n\n2. **[Scene 2 Name]** (5-15s)\n   [Brief description]\n\n3. **[Scene 3 Name]** (15-25s)\n   [Brief description]\n\n[... continue for all scenes]\n\n## Assets Needed\n### Required:\n- [Asset 1]\n- [Asset 2]\n\n### Optional:\n- [Asset 3]\n\n## Next Steps\nI can now generate the Remotion code and create your video. The process will:\n1. Generate React components for each scene\n2. Set up animations and transitions\n3. Integrate your assets\n4. Render to MP4\n\nWould you like me to proceed? Or would you like to adjust anything in the storyboard?\n```\n\n**Handle user response**:\n\n**\"Proceed\" \u002F \"Yes\" \u002F \"Looks good\"**:\n→ Move to Phase 5 (Code Generation)\n\n**\"Change [something]\"**:\n→ Update storyboard based on feedback\n→ Re-present for approval\n→ Then proceed when approved\n\n**\"I don't have [asset]\"**:\n→ Check if asset is required or optional\n→ If required: Ask user to provide or suggest alternative\n→ If optional: Note to skip that element in generation\n\n**\"Make it shorter\u002Flonger\"**:\n→ Re-invoke scene-planner with new duration\n→ Present updated storyboard\n\n---\n\n## Phase 5: Code Generation\n\n**Objective**: Generate complete Remotion project with React components for all scenes.\n\n**Project structure to create**:\n\n```\n$PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002F\n├── VideoComposition.tsx       # Main composition\n├── Scene1.tsx                 # Individual scenes\n├── Scene2.tsx\n├── Scene3.tsx\n...\n└── types.ts                   # TypeScript types (if needed)\n\n$PROJECT_DIR\u002Fsrc\u002FRoot.tsx # Updated with new composition\n```\n\n### Step 5.1: Create Root Component\n\n**File**: `$PROJECT_DIR\u002Fsrc\u002FRoot.tsx`\n\nCheck if file exists. If not, create:\n\n```typescript\nimport React from \"react\";\nimport { Composition } from \"remotion\";\n\nexport const RemotionRoot: React.FC = () => {\n  return \u003C>\u003C\u002F>;\n};\n```\n\nIf exists, read it to preserve other compositions.\n\nAdd new composition entry:\n\n```typescript\nimport { [VideoName]Composition } from \".\u002Fcompositions\u002F[video-name]\u002FVideoComposition\";\n\n\u002F\u002F Inside RemotionRoot return:\n\u003CComposition\n  id=\"[video-name]\"\n  component={[VideoName]Composition}\n  durationInFrames={[totalFrames]}\n  fps={30}\n  width={1920}\n  height={1080}\n  defaultProps={{}}\n\u002F>\n```\n\n**Naming convention**:\n- Composition ID: kebab-case (e.g., \"product-demo-2024\")\n- Component name: PascalCase (e.g., \"ProductDemo2024Composition\")\n\n### Step 5.2: Create Main Composition File\n\n**File**: `$PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002FVideoComposition.tsx`\n\n```typescript\nimport { AbsoluteFill, Sequence } from \"remotion\";\nimport { Scene1 } from \".\u002FScene1\";\nimport { Scene2 } from \".\u002FScene2\";\n\u002F\u002F Import all scene components\n\nexport const [VideoName]Composition: React.FC = () => {\n  return (\n    \u003CAbsoluteFill>\n      \u003CSequence from={0} durationInFrames={150}>\n        \u003CScene1 \u002F>\n      \u003C\u002FSequence>\n      \u003CSequence from={150} durationInFrames={360}>\n        \u003CScene2 \u002F>\n      \u003C\u002FSequence>\n      {\u002F* Add Sequence for each scene with correct timing *\u002F}\n    \u003C\u002FAbsoluteFill>\n  );\n};\n```\n\n**Key requirements**:\n- Use `\u003CSequence>` for each scene with correct `from` and `durationInFrames`\n- Import all scene components\n- Wrap in `\u003CAbsoluteFill>` for full-screen layout\n\n### Step 5.3: Generate Individual Scene Components\n\nFor each scene in the storyboard, create a separate component file.\n\n**File**: `$PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002FScene[N].tsx`\n\n**Scene component template**:\n\n```typescript\nimport { AbsoluteFill, useCurrentFrame, interpolate, spring, useVideoConfig } from \"remotion\";\n\nexport const Scene[N]: React.FC = () => {\n  const frame = useCurrentFrame();\n  const { fps } = useVideoConfig();\n  \n  \u002F\u002F Animation calculations using useCurrentFrame()\n  const opacity = interpolate(frame, [0, 30], [0, 1], {\n    extrapolateLeft: \"clamp\",\n    extrapolateRight: \"clamp\",\n  });\n  \n  const scale = spring({\n    frame,\n    fps,\n    config: {\n      damping: 100,\n      stiffness: 200,\n    },\n  });\n  \n  return (\n    \u003CAbsoluteFill\n      style={{\n        backgroundColor: \"[background-color]\",\n        justifyContent: \"center\",\n        alignItems: \"center\",\n        opacity,\n      }}\n    >\n      \u003Ch1\n        style={{\n          fontSize: [size],\n          fontWeight: [weight],\n          color: \"[color]\",\n          transform: `scale(${scale})`,\n          textAlign: \"center\",\n          padding: \"0 100px\",\n        }}\n      >\n        [Scene content]\n      \u003C\u002Fh1>\n    \u003C\u002FAbsoluteFill>\n  );\n};\n```\n\n**Component requirements based on scene type**:\n\n**Text Scene**:\n- Use `\u003Ch1>`, `\u003Ch2>`, `\u003Cp>` tags\n- Apply typography from design system\n- Implement fade-in\u002Fslide-in animations\n- Center align for titles, left align for body\n\n**Image Scene**:\n- Import `{ Img, staticFile }` from \"remotion\"\n- Use `\u003CImg src={staticFile(\"assets\u002F[filename]\")} \u002F>`\n- Apply scale or fade animations\n- Position with flexbox or absolute positioning\n\n**Split Scene** (text + image):\n- Use flexbox layout (flex-direction: row)\n- Left side: text content\n- Right side: image\n- Ensure responsive sizing\n\n**List\u002FBullets Scene**:\n- Map over array of items\n- Stagger animation timing for each item\n- Use interpolate for sequential reveals\n\n**Code example for staggered list**:\n```typescript\nconst items = [\"Item 1\", \"Item 2\", \"Item 3\"];\n\n{items.map((item, index) => {\n  const itemOpacity = interpolate(\n    frame,\n    [30 + index * 20, 45 + index * 20],\n    [0, 1],\n    { extrapolateLeft: \"clamp\", extrapolateRight: \"clamp\" }\n  );\n  \n  const itemX = interpolate(\n    frame,\n    [30 + index * 20, 50 + index * 20],\n    [-50, 0],\n    { extrapolateLeft: \"clamp\", extrapolateRight: \"clamp\" }\n  );\n  \n  return (\n    \u003Cdiv\n      key={index}\n      style={{\n        opacity: itemOpacity,\n        transform: `translateX(${itemX}px)`,\n        fontSize: 32,\n        marginBottom: 20,\n      }}\n    >\n      • {item}\n    \u003C\u002Fdiv>\n  );\n})}\n```\n\n### Step 5.4: Apply Remotion Best Practices\n\n**Critical rules to follow** (from remotion-best-practices skill):\n\n1. **Always use `useCurrentFrame()` for animations**:\n   ```typescript\n   const frame = useCurrentFrame();\n   \u002F\u002F Use frame for all animation calculations\n   ```\n\n2. **Never use CSS transitions or animations**:\n   ❌ `transition: opacity 0.3s`\n   ✅ `interpolate(frame, [0, 30], [0, 1])`\n\n3. **Use Remotion components for media**:\n   ❌ `\u003Cimg src=\"...\" \u002F>`\n   ✅ `\u003CImg src={staticFile(\"...\")} \u002F>`\n   \n   ❌ `\u003Cvideo src=\"...\" \u002F>`\n   ✅ `\u003CVideo src={staticFile(\"...\")} \u002F>`\n\n4. **Use staticFile() for assets**:\n   ❌ `src=\"..\u002F..\u002F..\u002Fpublic\u002Fassets\u002Flogo.png\"`\n   ✅ `src={staticFile(\"assets\u002Flogo.png\")}`\n\n5. **Use spring() for natural motion**:\n   ```typescript\n   const scale = spring({\n     frame,\n     fps,\n     config: { damping: 100, stiffness: 200 }\n   });\n   ```\n\n6. **Use interpolate() for linear animations**:\n   ```typescript\n   const opacity = interpolate(frame, [0, 30], [0, 1], {\n     extrapolateLeft: \"clamp\",\n     extrapolateRight: \"clamp\"\n   });\n   ```\n\n7. **Proper TypeScript typing**:\n   ```typescript\n   export const MyScene: React.FC = () => { ... }\n   ```\n\n### Step 5.5: Code Generation Strategy\n\n**Approach**: Generate clean, readable, well-commented code that follows best practices.\n\n**File creation order**:\n1. Create Root.tsx (or update if exists)\n2. Create VideoComposition.tsx\n3. Create Scene1.tsx, Scene2.tsx, etc. in sequence\n4. Create any helper components if needed\n\n**Code style**:\n- Use consistent indentation (2 spaces)\n- Add comments for complex animations\n- Use meaningful variable names\n- Group related style properties\n- Keep components focused (one scene per file)\n\n**Error prevention**:\n- Validate all frame calculations\n- Ensure cumulative timing matches storyboard\n- Check that asset paths are correct\n- Verify TypeScript types\n\n---\n\n## Phase 6: Asset Integration\n\n**Objective**: Copy user-provided assets to the correct location and update code references.\n\n**Process**:\n\n1. **Check which assets user provided**:\n   - Ask user: \"Please provide the following assets: [list]\"\n   - Or: \"Do you have these assets ready? If not, I can use placeholders.\"\n\n2. **Create assets directory** (if doesn't exist):\n   ```bash\n   mkdir -p \"$PROJECT_DIR\u002Fpublic\u002Fassets\"\n   ```\n\n3. **Copy assets**:\n   - User provides file paths\n   - Copy to public\u002Fassets\u002F directory:\n   ```bash\n   cp [user-path] \"$PROJECT_DIR\u002Fpublic\u002Fassets\u002F[filename]\"\n   ```\n\n4. **Verify assets**:\n   - Check file exists\n   - Check file size is reasonable (\u003C10MB for images)\n   - Check file format is supported (PNG, JPG, SVG for images)\n\n5. **Update code references**:\n   - Scenes already reference `staticFile(\"assets\u002F[filename]\")`\n   - Verify filename matches what was copied\n   - If user provided different filename, update code\n\n**If assets are missing**:\n\n**Required assets missing**:\n```\n⚠ The following required assets are missing:\n- Logo (logo.png)\n- Product screenshot (screenshot-1.png)\n\nPlease provide these files, or I can create placeholder elements so you can see the video structure.\n\nWould you like to:\n1. Provide the assets now\n2. Use placeholders for now (you can replace them later)\n3. Skip these elements\n```\n\n**Optional assets missing**:\n```\nℹ Note: These optional assets weren't provided:\n- Background music\n\nThe video will work without them, but they would enhance it. You can add them later if needed.\n```\n\n**Placeholder strategy**:\n- For logos: Use colored rectangle with text \"[Logo]\"\n- For images: Use colored background with text \"[Image: description]\"\n- For icons: Use Unicode emoji or simple shapes\n- User can replace placeholders later by swapping files\n\n---\n\n## Phase 7: Preview (Optional)\n\n**Objective**: Allow user to review the video before final rendering.\n\n**Remotion Studio approach**:\n\n1. **Start Remotion Studio**:\n   ```bash\n   cd \"$PROJECT_DIR\"\n   npm run dev\n   ```\n   \n   This starts a local server at `http:\u002F\u002Flocalhost:3000`\n\n2. **Inform user**:\n   ```\n   ✓ Video code generated successfully!\n   \n   Preview is now available at: http:\u002F\u002Flocalhost:3000\n   \n   You can:\n   - Scrub through the timeline\n   - Play\u002Fpause the video\n   - Adjust timing if needed\n   - See all animations in real-time\n   \n   When you're satisfied with the preview, let me know and I'll render the final MP4.\n   \n   (Or say \"skip preview\" to render directly)\n   ```\n\n3. **Wait for user feedback**:\n   - \"Looks good\" \u002F \"Render it\" → Proceed to Phase 8\n   - \"Change [something]\" → Make adjustments, regenerate code\n   - \"Skip preview\" → Proceed directly to Phase 8\n\n**Alternative: Skip preview**\n\nIf user is in a hurry or trusts the output:\n```\nWould you like to preview the video first, or should I render the final MP4 directly?\n\n1. Preview (recommended): See video in Remotion Studio\n2. Render directly: Skip to final MP4 (faster)\n```\n\nIf user chooses option 2, skip to Phase 8.\n\n---\n\n## Phase 8: Rendering\n\n**Objective**: Generate final MP4 file from Remotion project.\n\n**Process**:\n\n1. **Prepare render command**:\n   ```bash\n   cd \"$PROJECT_DIR\"\n   npx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4\n   ```\n\n2. **Start rendering**:\n   - Execute command\n   - Rendering may take 1-5 minutes depending on duration and complexity\n\n3. **Show progress** (if possible):\n   ```\n   Rendering video...\n   \n   [Progress bar if available]\n   \n   This may take a few minutes...\n   ```\n\n4. **Monitor for errors**:\n   - TypeScript compilation errors\n   - FFmpeg errors\n   - Asset not found errors\n   - Out of memory errors\n\n5. **Handle errors**:\n   \n   **TypeScript error**:\n   ```\n   ❌ Rendering failed: TypeScript error\n   \n   Error: [error message]\n   \n   Let me fix this...\n   ```\n   Fix the code issue and retry.\n   \n   **Asset not found**:\n   ```\n   ❌ Rendering failed: Asset not found\n   \n   Missing: assets\u002F[filename]\n   \n   Please provide this file or I can remove it from the video.\n   ```\n   \n   **FFmpeg error**:\n   ```\n   ❌ Rendering failed: FFmpeg error\n   \n   This usually means FFmpeg isn't properly installed.\n   Let me verify the environment...\n   ```\n   Re-run environment validation.\n\n6. **Rendering complete**:\n   ```\n   ✓ Rendering complete!\n   \n   Processing time: [X] minutes\n   Output file: $PROJECT_DIR\u002Foutput\u002F[video-name].mp4\n   ```\n\n**Rendering options**:\n\n**Standard quality** (default):\n```bash\ncd \"$PROJECT_DIR\"\nnpx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4\n```\n\n**High quality**:\n```bash\ncd \"$PROJECT_DIR\"\nnpx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4 --codec=h264-mkv --quality=100\n```\n\n**Fast preview** (lower quality, faster):\n```bash\ncd \"$PROJECT_DIR\"\nnpx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4 --jpeg-quality=50\n```\n\nChoose based on user needs (default to standard).\n\n---\n\n## Phase 9: Delivery\n\n**Objective**: Provide user with the final video and next steps.\n\n**Present results**:\n\n```\n🎬 Your video is ready!\n\n📁 Location: $PROJECT_DIR\u002Foutput\u002F[video-name].mp4\n⏱️  Duration: [X] seconds\n📐 Resolution: 1920x1080 (Full HD)\n💾 File Size: [Y] MB\n🎨 Scenes: [N] scenes\n\n✓ Generated [N] React components\n✓ Integrated [X] assets\n✓ Applied [Y] animations\n\nYou can now:\n1. Open the video: open \"$PROJECT_DIR\u002Foutput\u002F[video-name].mp4\"\n2. Upload to YouTube, Instagram, or other platforms\n3. Edit the source code to customize further (files in $PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002F)\n4. Re-render with changes: cd \"$PROJECT_DIR\" && npm run render\n\nNeed any adjustments? I can:\n- Change timing or animations\n- Add\u002Fremove scenes\n- Update colors or fonts\n- Regenerate with different content\n```\n\n**Provide full file path** so user can easily access:\n```bash\n# Full path (resolved at runtime)\nrealpath \"$PROJECT_DIR\u002Foutput\u002F[video-name].mp4\"\n```\n\n**Optional: Open video automatically**:\n```bash\nopen \"$PROJECT_DIR\u002Foutput\u002F[video-name].mp4\"\n```\n(macOS only; skip on Linux\u002FWindows)\n\n---\n\n## Customization and Iteration\n\n**If user wants to make changes**:\n\n### Scenario 1: Content changes\n\"Change the title text in scene 1\"\n\n**Action**:\n- Edit Scene1.tsx\n- Update text content\n- Re-run render command\n- Deliver updated video\n\n### Scenario 2: Timing adjustments\n\"Make scene 2 longer\"\n\n**Action**:\n- Update durationInFrames in VideoComposition.tsx\n- Adjust subsequent scene timings (shift from values)\n- Re-render\n- Deliver updated video\n\n### Scenario 3: Visual changes\n\"Use different colors\"\n\n**Action**:\n- Update color values in scene components\n- Re-render\n- Deliver updated video\n\n### Scenario 4: Add\u002Fremove scenes\n\"Add an intro scene\"\n\n**Action**:\n- Create new Scene0.tsx\n- Update VideoComposition.tsx to include new Sequence\n- Shift timing of subsequent scenes\n- Re-render\n- Deliver updated video\n\n**Quick edit workflow**:\n```\nFor quick edits, you can:\n1. Modify files in $PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002F\n2. Preview changes: npm run dev (opens Studio at localhost:3000)\n3. Re-render: npx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4\n\nLet me know what you'd like to change and I can update the code for you.\n```\n\n---\n\n## Error Handling & Recovery\n\n### Common Errors and Solutions\n\n**Error: \"Cannot find module 'remotion'\"**\n- **Cause**: Dependencies not installed\n- **Solution**: Re-run environment setup\n- **Command**: `cd \"$PROJECT_DIR\" && npm install`\n\n**Error: \"Composition not found\"**\n- **Cause**: Root.tsx not updated with new composition\n- **Solution**: Verify Root.tsx has correct import and Composition entry\n- **Fix**: Regenerate Root.tsx\n\n**Error: \"staticFile: File not found\"**\n- **Cause**: Asset doesn't exist at specified path\n- **Solution**: Verify asset exists in public\u002Fassets\u002F\n- **Command**: `ls \"$PROJECT_DIR\u002Fpublic\u002Fassets\u002F\"`\n\n**Error: \"FFmpeg exited with code 1\"**\n- **Cause**: FFmpeg error during encoding\n- **Solution**: Check FFmpeg installation, try different codec\n- **Command**: `ffmpeg -version`\n\n**Error: \"JavaScript heap out of memory\"**\n- **Cause**: Insufficient memory for rendering\n- **Solution**: Increase Node.js memory limit\n- **Command**: `export NODE_OPTIONS=\"--max-old-space-size=4096\"`\n\n**Error: TypeScript compilation errors**\n- **Cause**: Invalid TypeScript syntax in generated code\n- **Solution**: Fix syntax errors, ensure proper imports\n- **Action**: Review and correct the specific component\n\n### Graceful Degradation\n\nIf something fails:\n1. **Identify the issue**: Parse error message\n2. **Attempt fix**: Correct the specific problem\n3. **Retry**: Re-run the failed step\n4. **If still failing**: Provide clear error message and manual fix instructions\n5. **Fallback**: Offer to start over or skip problematic feature\n\n---\n\n## Best Practices\n\n### Code Quality\n\n**Generate clean code**:\n- Proper indentation and formatting\n- Meaningful variable names\n- Comments for complex logic\n- Consistent style throughout\n\n**Follow Remotion patterns**:\n- Use hooks correctly (useCurrentFrame, useVideoConfig)\n- Proper component structure\n- TypeScript types\n- Remotion-specific components\n\n**Performance considerations**:\n- Avoid heavy computations in render loop\n- Use memoization for expensive calculations\n- Optimize asset sizes\n- Efficient animation calculations\n\n### User Experience\n\n**Be proactive**:\n- Detect video intent automatically\n- Provide sensible defaults\n- Minimize required user input\n\n**Be transparent**:\n- Show what you're doing at each step\n- Explain rendering time\n- Report progress clearly\n\n**Be helpful**:\n- Offer preview before rendering\n- Provide file paths and commands\n- Suggest next steps\n- Enable easy customization\n\n**Be forgiving**:\n- Handle missing assets gracefully\n- Recover from errors\n- Offer alternatives when problems occur\n\n### Communication\n\n**Progress updates**:\n```\n✓ Environment ready\n✓ Storyboard created\n→ Generating code...\n```\n\n**Status indicators**:\n- ✓ Complete\n- → In progress\n- ⚠ Warning\n- ❌ Error\n- ℹ Information\n\n**Clear instructions**:\n- Provide exact commands\n- Show full file paths\n- Explain what each step does\n\n---\n\n## Integration with Other Skills\n\n### Uses environment-setup\n\nInvokes this skill first to ensure dependencies are installed.\n\n### Uses scene-planner\n\nInvokes this skill to create storyboard before code generation.\n\n### References remotion-best-practices\n\nApplies rules from this skill during code generation.\n\n### Reads templates\n\nReferences template files for structure and guidelines.\n\n---\n\n## Example Complete Workflow\n\n**User**: \"Create a 60-second explainer video about our AI writing assistant\"\n\n**Phase 1**: Environment check\n```\nChecking environment... ✓\nNode.js: v18.17.0 ✓\nFFmpeg: 6.0 ✓\nRemotion: 4.0.409 ✓\n```\n\n**Phase 2**: Requirements\n```\nI'll create an explainer video about your AI writing assistant.\n\nQuick questions:\n1. What's the main benefit users get? (e.g., \"Write 10x faster\", \"Never have writer's block\")\n2. Do you have a logo and any product screenshots?\n```\n\nUser provides: \"Main benefit is 'Write better content in half the time'. Yes, I have logo and 2 screenshots.\"\n\n**Phase 3**: Scene planning (internal - invokes scene-planner)\n\n**Phase 4**: Review\n```\nI've planned your explainer video:\n\nDuration: 60 seconds\nScenes: 6\n\n1. Hook (5s): \"Spending hours on every article?\"\n2. Problem (10s): Writer's block, slow writing, quality concerns\n3. Solution (8s): Introduce AI Writing Assistant\n4. How It Works (22s): 3 steps - Input topic, AI generates draft, Edit and publish\n5. Benefits (10s): Save time, improve quality, overcome blocks\n6. CTA (5s): \"Start writing better at [website].com\"\n\nAssets needed:\n- Logo ✓ (you have)\n- 2 product screenshots ✓ (you have)\n\nShall I proceed with generating the video?\n```\n\nUser: \"Yes, proceed\"\n\n**Phase 5**: Code generation\n```\nGenerating Remotion code...\n✓ Created VideoComposition.tsx\n✓ Created 6 scene components\n✓ Updated Root.tsx\n```\n\n**Phase 6**: Assets\n```\nPlease provide your assets:\n1. Logo file path:\n2. Screenshot 1 file path:\n3. Screenshot 2 file path:\n```\n\nUser provides paths. Assets copied.\n\n```\n✓ Integrated 3 assets\n```\n\n**Phase 7**: Preview\n```\n✓ Code generation complete!\n\nPreview available at: http:\u002F\u002Flocalhost:3000\n\nReview the video and let me know when ready to render final MP4.\n```\n\nUser reviews: \"Looks great, render it!\"\n\n**Phase 8**: Rendering\n```\nRendering video...\n[Progress bar]\n✓ Rendering complete! (took 2 minutes)\n```\n\n**Phase 9**: Delivery\n```\n🎬 Your video is ready!\n\n📁 $PROJECT_DIR\u002Foutput\u002Fai-writing-assistant-explainer.mp4\n⏱️  60 seconds\n📐 1920x1080 (Full HD)\n💾 15.3 MB\n🎨 6 scenes\n\nOpen video: open \"$PROJECT_DIR\u002Foutput\u002Fai-writing-assistant-explainer.mp4\"\n\nNeed changes? Let me know!\n```\n\n**Total time**: ~5 minutes (including rendering)\n\n---\n\n## Advanced Features (Future Enhancements)\n\nPotential future capabilities:\n\n**Voice-over generation**: Integrate text-to-speech\n**Subtitle generation**: Automatic captions\n**Multiple formats**: Render 16:9, 9:16, 1:1 simultaneously\n**Batch generation**: Create multiple videos from template\n**A\u002FB variants**: Generate multiple versions with variations\n**Direct upload**: Publish to YouTube\u002FInstagram via API\n\n---\n\n## Community-Driven Best Practices Integration\n\n> These practices are sourced from the most successful Remotion video toolkits in the community:\n> - remotion-dev\u002Ftemplate-prompt-to-motion-graphics (81 stars)\n> - digitalsamba\u002Fclaude-code-video-toolkit (40 stars)\n> - wshuyi\u002Fremotion-video-skill (70 stars)\n> - JJenglert1\u002Fremotion-claude-video (16 stars)\n\n### Constants-First Design (MANDATORY)\n\nAll generated code MUST place editable values at the top of each file:\n\n```typescript\n\u002F\u002F ============ EDITABLE CONSTANTS ============\nconst BRAND = {\n  primaryColor: '#2563EB',\n  accentColor: '#F97316',\n  backgroundColor: '#0F172A',\n  textColor: '#F8FAFC',\n};\n\nconst TYPOGRAPHY = {\n  headingFont: 'Inter',\n  bodyFont: 'Inter',\n  headingSize: 72,\n  bodySize: 28,\n  headingWeight: 700,\n  bodyWeight: 400,\n};\n\nconst CONTENT = {\n  title: 'Your Title Here',\n  subtitle: 'Your subtitle',\n  items: ['Point 1', 'Point 2', 'Point 3'],\n};\n\nconst TIMING = {\n  fps: 30,\n  sceneDurations: [150, 300, 240, 180],\n};\n\u002F\u002F ============================================\n```\n\n**Why**: Users can quickly customize videos by editing only the constant block, without understanding component internals. This is the single most impactful practice from the community.\n\n### Skill Detection and Injection\n\nBefore generating code, analyze the video requirements and inject only relevant Remotion best-practice rules:\n\n| Video Need | Rules to Reference |\n|------------|-------------------|\n| Text animations | `remotion-best-practices\u002Frules\u002Ftext-animations.md` |\n| Scene transitions | `remotion-best-practices\u002Frules\u002Ftransitions.md` |\n| Spring physics | `remotion-best-practices\u002Frules\u002Ftiming.md` |\n| Image handling | `remotion-best-practices\u002Frules\u002Fimages.md` |\n| Captions | `remotion-best-practices\u002Frules\u002Fdisplay-captions.md` |\n| Font loading | `remotion-best-practices\u002Frules\u002Fmeasuring-text.md` |\n| Parameters | `remotion-best-practices\u002Frules\u002Fparameters.md` |\n\nThis prevents context bloat while ensuring relevant expertise is applied.\n\n### Prompt Library Integration\n\nReference the prompt library at `${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002Fprompt-library\u002F` for:\n\n- **00-director-prompt.md**: System-level director prompt (inject for every video)\n- **01-product-launch.md**: Product launch \u002F feature announcement videos\n- **02-developer-tool-promo.md**: Open source \u002F developer tool promotions\n- **03-data-ranking.md**: Data charts and ranking animations\n- **04-kinetic-typography.md**: Quote and kinetic text videos\n- **05-app-walkthrough.md**: App UI demonstrations\n- **06-before-after.md**: Before vs After comparisons\n- **07-release-announcement.md**: Changelog \u002F version release videos\n- **08-thread-summary.md**: Thread \u002F post summary videos\n- **09-polish-prompts.md**: Post-generation quality enhancement\n\n### Iterative Quality Enhancement\n\nAfter initial code generation, apply a structured polish process:\n\n**Round 1: Structure** — Timeline logic, reading time, holds\n**Round 2: Visual** — Design system unity (fonts, colors, spacing)\n**Round 3: Animation** — Spring physics, stagger timing, background motion\n**Round 4: Detail** — Shadows, safe zones, contrast ratios\n\nReference `${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002Fprompt-library\u002F09-polish-prompts.md` for specific polish instructions.\n\n### Anti-Pattern Prevention\n\nDuring code generation, actively avoid these documented anti-patterns:\n\n**Text Animation Anti-Patterns**:\n- ❌ Per-character opacity for typewriter effect → ✅ Use `text.slice(0, n)`\n- ❌ Abrupt cursor blink (Math.round) → ✅ Smooth interpolated opacity\n- ❌ Word carousel without fixed width → ✅ Measure longest word, set fixed container\n\n**Transition Anti-Patterns**:\n- ❌ Hard cuts between scenes → ✅ Always crossfade (15-25 frames)\n- ❌ Transition duration > 45 frames → ✅ Keep transitions 15-25 frames\n\n**Animation Anti-Patterns**:\n- ❌ CSS transition\u002Fanimation → ✅ useCurrentFrame() + interpolate\u002Fspring\n- ❌ Linear easing for everything → ✅ spring() for key actions, linear only for constant motion\n- ❌ interpolate without clamp → ✅ Always add extrapolateLeft\u002FRight: 'clamp'\n\n**Resource Anti-Patterns**:\n- ❌ HTML `\u003Cimg>` tag → ✅ Remotion `\u003CImg>` component\n- ❌ Hardcoded file paths → ✅ `staticFile(\"assets\u002Ffile.png\")`\n- ❌ Spring config inline → ✅ Cache as constants\n\n### Reusable Animation Utilities\n\nGenerate these utility functions at the top of the composition or in a shared utils file:\n\n```typescript\n\u002F\u002F Fade + slide up (most common entrance)\nconst fadeSlideUp = (frame: number, start: number, duration = 20) => ({\n  opacity: interpolate(frame, [start, start + duration], [0, 1], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  }),\n  transform: `translateY(${interpolate(frame, [start, start + duration + 5], [30, 0], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  })}px)`,\n});\n\n\u002F\u002F Staggered list item reveal\nconst staggerItem = (frame: number, index: number, gap = 15) => ({\n  opacity: interpolate(frame, [index * gap, index * gap + 20], [0, 1], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  }),\n  transform: `translateX(${interpolate(frame, [index * gap, index * gap + 25], [-40, 0], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  })}px)`,\n});\n\n\u002F\u002F Typewriter text reveal\nconst typewriter = (frame: number, text: string, speed = 2) =>\n  text.slice(0, Math.min(Math.floor(frame \u002F speed), text.length));\n\n\u002F\u002F Count-up number animation\nconst countUp = (frame: number, target: number, start: number, duration: number) =>\n  Math.floor(target * interpolate(frame, [start, start + duration], [0, 1], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  }));\n```\n\n### Font Loading Best Practice\n\nAlways use `@remotion\u002Fgoogle-fonts` for font loading:\n\n```typescript\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FInter\";\nconst { fontFamily } = loadFont();\n\n\u002F\u002F Then use in styles:\nstyle={{ fontFamily }}\n```\n\nFor code\u002Fterminal scenes:\n```typescript\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FJetBrainsMono\";\nconst { fontFamily: monoFont } = loadFont();\n```\n\n---\n\n## Expanded Video Type Support\n\nBeyond the 4 core types (explainer, product demo, social media, presentation), this skill supports 10 additional high-impact video styles, each with a full **structural template** (`${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002F`) AND a **prompt library entry** (`${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002Fprompt-library\u002F`):\n\n| Video Type | Template | Prompt Library | Duration |\n|---|---|---|---|\n| Product Launch | `templates\u002Fproduct-launch.md` | `prompt-library\u002F01-product-launch.md` | 10-15s |\n| Open Source Promo | `templates\u002Fopen-source-promo.md` | `prompt-library\u002F02-developer-tool-promo.md` | 15-30s |\n| Data Ranking | `templates\u002Fdata-ranking.md` | `prompt-library\u002F03-data-ranking.md` | 15-30s |\n| Kinetic Typography | `templates\u002Fkinetic-typography.md` | `prompt-library\u002F04-kinetic-typography.md` | 15-60s |\n| App Walkthrough | `templates\u002Fapp-walkthrough.md` | `prompt-library\u002F05-app-walkthrough.md` | 30-60s |\n| Before\u002FAfter | `templates\u002Fbefore-after.md` | `prompt-library\u002F06-before-after.md` | 10-20s |\n| Release Announcement | `templates\u002Frelease-announcement.md` | `prompt-library\u002F07-release-announcement.md` | 15-30s |\n| Thread Summary | `templates\u002Fthread-summary.md` | `prompt-library\u002F08-thread-summary.md` | 20-45s |\n| Map Route | `templates\u002Fmap-route.md` | — | 15-30s |\n| Music Visualization | `templates\u002Fmusic-visualization.md` | — | Matches audio |\n\n**How to use**: For each extended type, read BOTH the structural template (for scene breakdown, layout, animation code patterns) AND the prompt library entry (for user-facing prompt format, Constants-First code skeleton). The template provides the \"how\", the prompt library provides the \"what to ask\".\n\n---\n\nThis skill represents the complete orchestration layer that makes video generation seamless and automated for users. By coordinating environment setup, storyboarding, code generation, and rendering — and applying community-proven best practices like Constants-First Design, skill injection, and structured polish rounds — it transforms user ideas into production-ready, visually polished videos with minimal manual intervention.\n","# Remotion Video Generator\n\nYou are the primary orchestrator for automated video generation using Remotion. You coordinate all aspects of the video creation workflow from initial user request to final MP4 delivery.\n\n## When This Skill Activates\n\nThis skill should activate **automatically** when user input contains any of these patterns:\n\n### Explicit Video Requests\n- \"create a video\"\n- \"generate a video\" \n- \"make a video\"\n- \"build a video\"\n- \"produce a video\"\n- \"render a video\"\n- \"我需要一个视频\"\n- \"帮我做个视频\"\n- \"生成视频\"\n\n### Video Type Keywords\n- \"explainer video\"\n- \"product demo\"\n- \"demo video\"\n- \"product video\"\n- \"tutorial video\"\n- \"promotional video\"\n- \"marketing video\"\n- \"social media video\"\n- \"Instagram Reel\"\n- \"TikTok video\"\n- \"YouTube Short\"\n- \"presentation video\"\n- \"slide video\"\n\n### Animation Keywords\n- \"animate this\"\n- \"animated video\"\n- \"motion graphics\"\n- \"video animation\"\n\n### Implicit Requests\n- \"show this as a video\"\n- \"visualize this\"\n- \"I need something to post on Instagram\"\n- \"turn these slides into a video\"\n\n**Important**: Activation should be permissive. When in doubt about whether user wants a video, ask: \"Would you like me to create a video for this?\"\n\n---\n\n## Core Workflow\n\nThe complete video generation process follows these steps:\n\n### Phase 1: Environment Validation\n### Phase 2: Requirements Gathering  \n### Phase 3: Scene Planning\n### Phase 4: Storyboard Review\n### Phase 5: Code Generation\n### Phase 6: Asset Integration\n### Phase 7: Preview (Optional)\n### Phase 8: Rendering\n### Phase 9: Delivery\n\n---\n\n## Phase 1: Environment Validation\n\n**Objective**: Ensure the system has all required dependencies installed.\n\n**Process**:\n\n1. **Check if environment exists**:\n   ```bash\n   # PROJECT_DIR is determined by the environment-setup skill\n   # Default: .\u002Fremotion-videos (current working directory)\n   PROJECT_DIR=\"${REMOTION_PROJECT_DIR:-.\u002Fremotion-videos}\"\n   ls \"$PROJECT_DIR\u002Fnode_modules\u002Fremotion\"\n   ```\n   \n   - If exists and recent (check within last 24 hours): Skip validation, proceed\n   - If doesn't exist or old: Run full validation\n\n2. **Invoke environment-setup skill**:\n   - This skill handles all dependency checking and installation\n   - Wait for completion signal\n   - Handle three possible outcomes:\n     - **Ready**: All requirements met → Proceed to Phase 2\n     - **Pending**: User needs to complete manual installation → Wait for user\n     - **Failed**: Cannot proceed → Inform user and stop\n\n3. **If environment setup fails**:\n   ```\n   ❌ Unable to set up video generation environment.\n   \n   Missing requirements:\n   [List from environment-setup skill]\n   \n   Please install the missing requirements and try again, or I can guide you through the installation process.\n   ```\n\n**Success criteria**: Node.js, FFmpeg, and Remotion packages are all installed and accessible.\n\n---\n\n## Phase 2: Requirements Gathering\n\n**Objective**: Extract all necessary information from user input.\n\n**What to extract**:\n\n### Essential Information\n\n1. **Video purpose\u002Fgoal**:\n   - What should the video accomplish?\n   - Example: \"Explain our product\", \"Promote a sale\", \"Present quarterly results\"\n\n2. **Key content\u002Fmessages**:\n   - What information should be included?\n   - Main points to communicate (extract 3-5 key points)\n\n3. **Duration**:\n   - How long should the video be?\n   - If not specified, use defaults based on type:\n     - Explainer: 60 seconds\n     - Product demo: 60 seconds\n     - Social media: 30 seconds\n     - Presentation: 120 seconds\n\n### Additional Context (if available)\n\n4. **Target audience**: Who will watch this?\n5. **Visual style**: Professional, creative, minimal, bold?\n6. **Brand elements**: Colors, fonts, logo\n7. **Available assets**: Images, videos, audio files\n8. **Platform**: Where will this be posted? (YouTube, Instagram, etc.)\n\n### Smart Information Extraction\n\n**If user provides detailed description**, extract all relevant information:\n\nExample input: *\"Create a 90-second explainer video about our AI chatbot. Show how it helps customer support teams save time. Use our brand colors: blue #2563EB and white. I have our logo and 3 product screenshots.\"*\n\nExtract:\n- Type: Explainer video\n- Duration: 90 seconds\n- Topic: AI chatbot for customer support\n- Key message: Saves time for support teams\n- Brand colors: Blue #2563EB, White\n- Assets: Logo + 3 screenshots\n\n**If user provides minimal description**, use intelligent defaults:\n\nExample input: *\"Make a video about our new feature\"*\n\nInfer:\n- Type: Product demo (feature showcase)\n- Duration: 60 seconds (default)\n- Topic: New feature\n- Need to ask: \"What's the feature and what makes it special?\"\n\n### When to Ask Clarifying Questions\n\n**Always ask** if these are unclear:\n- What the video is about (core topic\u002Fmessage)\n- Duration (if user has strong preference)\n\n**Consider asking** if helpful but not critical:\n- Specific assets available\n- Brand colors\n- Target platform\n\n**Never ask** if you can reasonably infer:\n- Video type (usually obvious from context)\n- Style (default to professional)\n- Technical specs (use defaults)\n\n### Example Clarifying Questions\n\n**Minimal approach** (preferred - ask only what's needed):\n```\nI'll create a [video type] for you. To make it effective, I need to know:\n\n1. What's the main message or goal?\n2. How long should it be?\n3. Do you have any images, logos, or other assets I should include?\n```\n\n**Targeted approach** (when specific info is needed):\n```\nI'll create a product demo video showcasing [feature]. \n\nQuick questions:\n- What 3 key benefits should I highlight?\n- Do you have product screenshots I can use?\n```\n\n---\n\n## Phase 3: Scene Planning\n\n**Objective**: Create detailed storyboard with all visual and timing specifications.\n\n**Process**:\n\n1. **Invoke scene-planner skill** with gathered requirements:\n   ```\n   Create a storyboard for:\n   - Type: [explainer\u002Fdemo\u002Fsocial\u002Fpresentation]\n   - Duration: [X] seconds\n   - Topic: [description]\n   - Key messages: [list]\n   - Brand colors: [if provided]\n   - Available assets: [list]\n   ```\n\n2. **Receive storyboard** from scene-planner:\n   - Scene-by-scene breakdown\n   - Timing specifications\n   - Visual design system\n   - Animation details\n   - Asset requirements\n\n3. **Process storyboard internally**:\n   - Parse scene specifications\n   - Note required vs. optional assets\n   - Prepare for code generation\n\n**Output from this phase**: Complete storyboard specification ready for implementation.\n\n---\n\n## Phase 4: Storyboard Review\n\n**Objective**: Show user the plan before generating code.\n\n**Present storyboard in user-friendly format**:\n\n```markdown\nI've planned your [video type]:\n\n## Overview\n- **Duration**: [X] seconds\n- **Scenes**: [N] scenes\n- **Style**: [Professional\u002FCreative\u002FModern]\n- **Resolution**: 1920x1080 (Full HD)\n\n## Scene Flow\n1. **[Scene 1 Name]** (0-5s)\n   [Brief description of what happens]\n\n2. **[Scene 2 Name]** (5-15s)\n   [Brief description]\n\n3. **[Scene 3 Name]** (15-25s)\n   [Brief description]\n\n[... continue for all scenes]\n\n## Assets Needed\n### Required:\n- [Asset 1]\n- [Asset 2]\n\n### Optional:\n- [Asset 3]\n\n## Next Steps\nI can now generate the Remotion code and create your video. The process will:\n1. Generate React components for each scene\n2. Set up animations and transitions\n3. Integrate your assets\n4. Render to MP4\n\nWould you like me to proceed? Or would you like to adjust anything in the storyboard?\n```\n\n**Handle user response**:\n\n**\"Proceed\" \u002F \"Yes\" \u002F \"Looks good\"**:\n→ Move to Phase 5 (Code Generation)\n\n**\"Change [something]\"**:\n→ Update storyboard based on feedback\n→ Re-present for approval\n→ Then proceed when approved\n\n**\"I don't have [asset]\"**:\n→ Check if asset is required or optional\n→ If required: Ask user to provide or suggest alternative\n→ If optional: Note to skip that element in generation\n\n**\"Make it shorter\u002Flonger\"**:\n→ Re-invoke scene-planner with new duration\n→ Present updated storyboard\n\n---\n\n## Phase 5: Code Generation\n\n**Objective**: Generate complete Remotion project with React components for all scenes.\n\n**Project structure to create**:\n\n```\n$PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002F\n├── VideoComposition.tsx       # Main composition\n├── Scene1.tsx                 # Individual scenes\n├── Scene2.tsx\n├── Scene3.tsx\n...\n└── types.ts                   # TypeScript types (if needed)\n\n$PROJECT_DIR\u002Fsrc\u002FRoot.tsx # Updated with new composition\n```\n\n### Step 5.1: Create Root Component\n\n**File**: `$PROJECT_DIR\u002Fsrc\u002FRoot.tsx`\n\nCheck if file exists. If not, create:\n\n```typescript\nimport React from \"react\";\nimport { Composition } from \"remotion\";\n\nexport const RemotionRoot: React.FC = () => {\n  return \u003C>\u003C\u002F>;\n};\n```\n\nIf exists, read it to preserve other compositions.\n\nAdd new composition entry:\n\n```typescript\nimport { [VideoName]Composition } from \".\u002Fcompositions\u002F[video-name]\u002FVideoComposition\";\n\n\u002F\u002F Inside RemotionRoot return:\n\u003CComposition\n  id=\"[video-name]\"\n  component={[VideoName]Composition}\n  durationInFrames={[totalFrames]}\n  fps={30}\n  width={1920}\n  height={1080}\n  defaultProps={{}}\n\u002F>\n```\n\n**Naming convention**:\n- Composition ID: kebab-case (e.g., \"product-demo-2024\")\n- Component name: PascalCase (e.g., \"ProductDemo2024Composition\")\n\n### Step 5.2: Create Main Composition File\n\n**File**: `$PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002FVideoComposition.tsx`\n\n```typescript\nimport { AbsoluteFill, Sequence } from \"remotion\";\nimport { Scene1 } from \".\u002FScene1\";\nimport { Scene2 } from \".\u002FScene2\";\n\u002F\u002F Import all scene components\n\nexport const [VideoName]Composition: React.FC = () => {\n  return (\n    \u003CAbsoluteFill>\n      \u003CSequence from={0} durationInFrames={150}>\n        \u003CScene1 \u002F>\n      \u003C\u002FSequence>\n      \u003CSequence from={150} durationInFrames={360}>\n        \u003CScene2 \u002F>\n      \u003C\u002FSequence>\n      {\u002F* Add Sequence for each scene with correct timing *\u002F}\n    \u003C\u002FAbsoluteFill>\n  );\n};\n```\n\n**Key requirements**:\n- Use `\u003CSequence>` for each scene with correct `from` and `durationInFrames`\n- Import all scene components\n- Wrap in `\u003CAbsoluteFill>` for full-screen layout\n\n### Step 5.3: Generate Individual Scene Components\n\nFor each scene in the storyboard, create a separate component file.\n\n**File**: `$PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002FScene[N].tsx`\n\n**Scene component template**:\n\n```typescript\nimport { AbsoluteFill, useCurrentFrame, interpolate, spring, useVideoConfig } from \"remotion\";\n\nexport const Scene[N]: React.FC = () => {\n  const frame = useCurrentFrame();\n  const { fps } = useVideoConfig();\n  \n  \u002F\u002F Animation calculations using useCurrentFrame()\n  const opacity = interpolate(frame, [0, 30], [0, 1], {\n    extrapolateLeft: \"clamp\",\n    extrapolateRight: \"clamp\",\n  });\n  \n  const scale = spring({\n    frame,\n    fps,\n    config: {\n      damping: 100,\n      stiffness: 200,\n    },\n  });\n  \n  return (\n    \u003CAbsoluteFill\n      style={{\n        backgroundColor: \"[background-color]\",\n        justifyContent: \"center\",\n        alignItems: \"center\",\n        opacity,\n      }}\n    >\n      \u003Ch1\n        style={{\n          fontSize: [size],\n          fontWeight: [weight],\n          color: \"[color]\",\n          transform: `scale(${scale})`,\n          textAlign: \"center\",\n          padding: \"0 100px\",\n        }}\n      >\n        [Scene content]\n      \u003C\u002Fh1>\n    \u003C\u002FAbsoluteFill>\n  );\n};\n```\n\n**Component requirements based on scene type**:\n\n**Text Scene**:\n- Use `\u003Ch1>`, `\u003Ch2>`, `\u003Cp>` tags\n- Apply typography from design system\n- Implement fade-in\u002Fslide-in animations\n- Center align for titles, left align for body\n\n**Image Scene**:\n- Import `{ Img, staticFile }` from \"remotion\"\n- Use `\u003CImg src={staticFile(\"assets\u002F[filename]\")} \u002F>`\n- Apply scale or fade animations\n- Position with flexbox or absolute positioning\n\n**Split Scene** (text + image):\n- Use flexbox layout (flex-direction: row)\n- Left side: text content\n- Right side: image\n- Ensure responsive sizing\n\n**List\u002FBullets Scene**:\n- Map over array of items\n- Stagger animation timing for each item\n- Use interpolate for sequential reveals\n\n**Code example for staggered list**:\n```typescript\nconst items = [\"Item 1\", \"Item 2\", \"Item 3\"];\n\n{items.map((item, index) => {\n  const itemOpacity = interpolate(\n    frame,\n    [30 + index * 20, 45 + index * 20],\n    [0, 1],\n    { extrapolateLeft: \"clamp\", extrapolateRight: \"clamp\" }\n  );\n  \n  const itemX = interpolate(\n    frame,\n    [30 + index * 20, 50 + index * 20],\n    [-50, 0],\n    { extrapolateLeft: \"clamp\", extrapolateRight: \"clamp\" }\n  );\n  \n  return (\n    \u003Cdiv\n      key={index}\n      style={{\n        opacity: itemOpacity,\n        transform: `translateX(${itemX}px)`,\n        fontSize: 32,\n        marginBottom: 20,\n      }}\n    >\n      • {item}\n    \u003C\u002Fdiv>\n  );\n})}\n```\n\n### Step 5.4: Apply Remotion Best Practices\n\n**Critical rules to follow** (from remotion-best-practices skill):\n\n1. **Always use `useCurrentFrame()` for animations**:\n   ```typescript\n   const frame = useCurrentFrame();\n   \u002F\u002F Use frame for all animation calculations\n   ```\n\n2. **Never use CSS transitions or animations**:\n   ❌ `transition: opacity 0.3s`\n   ✅ `interpolate(frame, [0, 30], [0, 1])`\n\n3. **Use Remotion components for media**:\n   ❌ `\u003Cimg src=\"...\" \u002F>`\n   ✅ `\u003CImg src={staticFile(\"...\")} \u002F>`\n   \n   ❌ `\u003Cvideo src=\"...\" \u002F>`\n   ✅ `\u003CVideo src={staticFile(\"...\")} \u002F>`\n\n4. **Use staticFile() for assets**:\n   ❌ `src=\"..\u002F..\u002F..\u002Fpublic\u002Fassets\u002Flogo.png\"`\n   ✅ `src={staticFile(\"assets\u002Flogo.png\")}`\n\n5. **Use spring() for natural motion**:\n   ```typescript\n   const scale = spring({\n     frame,\n     fps,\n     config: { damping: 100, stiffness: 200 }\n   });\n   ```\n\n6. **Use interpolate() for linear animations**:\n   ```typescript\n   const opacity = interpolate(frame, [0, 30], [0, 1], {\n     extrapolateLeft: \"clamp\",\n     extrapolateRight: \"clamp\"\n   });\n   ```\n\n7. **Proper TypeScript typing**:\n   ```typescript\n   export const MyScene: React.FC = () => { ... }\n   ```\n\n### Step 5.5: Code Generation Strategy\n\n**Approach**: Generate clean, readable, well-commented code that follows best practices.\n\n**File creation order**:\n1. Create Root.tsx (or update if exists)\n2. Create VideoComposition.tsx\n3. Create Scene1.tsx, Scene2.tsx, etc. in sequence\n4. Create any helper components if needed\n\n**Code style**:\n- Use consistent indentation (2 spaces)\n- Add comments for complex animations\n- Use meaningful variable names\n- Group related style properties\n- Keep components focused (one scene per file)\n\n**Error prevention**:\n- Validate all frame calculations\n- Ensure cumulative timing matches storyboard\n- Check that asset paths are correct\n- Verify TypeScript types\n\n---\n\n## Phase 6: Asset Integration\n\n**Objective**: Copy user-provided assets to the correct location and update code references.\n\n**Process**:\n\n1. **Check which assets user provided**:\n   - Ask user: \"Please provide the following assets: [list]\"\n   - Or: \"Do you have these assets ready? If not, I can use placeholders.\"\n\n2. **Create assets directory** (if doesn't exist):\n   ```bash\n   mkdir -p \"$PROJECT_DIR\u002Fpublic\u002Fassets\"\n   ```\n\n3. **Copy assets**:\n   - User provides file paths\n   - Copy to public\u002Fassets\u002F directory:\n   ```bash\n   cp [user-path] \"$PROJECT_DIR\u002Fpublic\u002Fassets\u002F[filename]\"\n   ```\n\n4. **Verify assets**:\n   - Check file exists\n   - Check file size is reasonable (\u003C10MB for images)\n   - Check file format is supported (PNG, JPG, SVG for images)\n\n5. **Update code references**:\n   - Scenes already reference `staticFile(\"assets\u002F[filename]\")`\n   - Verify filename matches what was copied\n   - If user provided different filename, update code\n\n**If assets are missing**:\n\n**Required assets missing**:\n```\n⚠ The following required assets are missing:\n- Logo (logo.png)\n- Product screenshot (screenshot-1.png)\n\nPlease provide these files, or I can create placeholder elements so you can see the video structure.\n\nWould you like to:\n1. Provide the assets now\n2. Use placeholders for now (you can replace them later)\n3. Skip these elements\n```\n\n**Optional assets missing**:\n```\nℹ Note: These optional assets weren't provided:\n- Background music\n\nThe video will work without them, but they would enhance it. You can add them later if needed.\n```\n\n**Placeholder strategy**:\n- For logos: Use colored rectangle with text \"[Logo]\"\n- For images: Use colored background with text \"[Image: description]\"\n- For icons: Use Unicode emoji or simple shapes\n- User can replace placeholders later by swapping files\n\n---\n\n## Phase 7: Preview (Optional)\n\n**Objective**: Allow user to review the video before final rendering.\n\n**Remotion Studio approach**:\n\n1. **Start Remotion Studio**:\n   ```bash\n   cd \"$PROJECT_DIR\"\n   npm run dev\n   ```\n   \n   This starts a local server at `http:\u002F\u002Flocalhost:3000`\n\n2. **Inform user**:\n   ```\n   ✓ Video code generated successfully!\n   \n   Preview is now available at: http:\u002F\u002Flocalhost:3000\n   \n   You can:\n   - Scrub through the timeline\n   - Play\u002Fpause the video\n   - Adjust timing if needed\n   - See all animations in real-time\n   \n   When you're satisfied with the preview, let me know and I'll render the final MP4.\n   \n   (Or say \"skip preview\" to render directly)\n   ```\n\n3. **Wait for user feedback**:\n   - \"Looks good\" \u002F \"Render it\" → Proceed to Phase 8\n   - \"Change [something]\" → Make adjustments, regenerate code\n   - \"Skip preview\" → Proceed directly to Phase 8\n\n**Alternative: Skip preview**\n\nIf user is in a hurry or trusts the output:\n```\nWould you like to preview the video first, or should I render the final MP4 directly?\n\n1. Preview (recommended): See video in Remotion Studio\n2. Render directly: Skip to final MP4 (faster)\n```\n\nIf user chooses option 2, skip to Phase 8.\n\n---\n\n## Phase 8: Rendering\n\n**Objective**: Generate final MP4 file from Remotion project.\n\n**Process**:\n\n1. **Prepare render command**:\n   ```bash\n   cd \"$PROJECT_DIR\"\n   npx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4\n   ```\n\n2. **Start rendering**:\n   - Execute command\n   - Rendering may take 1-5 minutes depending on duration and complexity\n\n3. **Show progress** (if possible):\n   ```\n   Rendering video...\n   \n   [Progress bar if available]\n   \n   This may take a few minutes...\n   ```\n\n4. **Monitor for errors**:\n   - TypeScript compilation errors\n   - FFmpeg errors\n   - Asset not found errors\n   - Out of memory errors\n\n5. **Handle errors**:\n   \n   **TypeScript error**:\n   ```\n   ❌ Rendering failed: TypeScript error\n   \n   Error: [error message]\n   \n   Let me fix this...\n   ```\n   Fix the code issue and retry.\n   \n   **Asset not found**:\n   ```\n   ❌ Rendering failed: Asset not found\n   \n   Missing: assets\u002F[filename]\n   \n   Please provide this file or I can remove it from the video.\n   ```\n   \n   **FFmpeg error**:\n   ```\n   ❌ Rendering failed: FFmpeg error\n   \n   This usually means FFmpeg isn't properly installed.\n   Let me verify the environment...\n   ```\n   Re-run environment validation.\n\n6. **Rendering complete**:\n   ```\n   ✓ Rendering complete!\n   \n   Processing time: [X] minutes\n   Output file: $PROJECT_DIR\u002Foutput\u002F[video-name].mp4\n   ```\n\n**Rendering options**:\n\n**Standard quality** (default):\n```bash\ncd \"$PROJECT_DIR\"\nnpx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4\n```\n\n**High quality**:\n```bash\ncd \"$PROJECT_DIR\"\nnpx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4 --codec=h264-mkv --quality=100\n```\n\n**Fast preview** (lower quality, faster):\n```bash\ncd \"$PROJECT_DIR\"\nnpx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4 --jpeg-quality=50\n```\n\nChoose based on user needs (default to standard).\n\n---\n\n## Phase 9: Delivery\n\n**Objective**: Provide user with the final video and next steps.\n\n**Present results**:\n\n```\n🎬 Your video is ready!\n\n📁 Location: $PROJECT_DIR\u002Foutput\u002F[video-name].mp4\n⏱️  Duration: [X] seconds\n📐 Resolution: 1920x1080 (Full HD)\n💾 File Size: [Y] MB\n🎨 Scenes: [N] scenes\n\n✓ Generated [N] React components\n✓ Integrated [X] assets\n✓ Applied [Y] animations\n\nYou can now:\n1. Open the video: open \"$PROJECT_DIR\u002Foutput\u002F[video-name].mp4\"\n2. Upload to YouTube, Instagram, or other platforms\n3. Edit the source code to customize further (files in $PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002F)\n4. Re-render with changes: cd \"$PROJECT_DIR\" && npm run render\n\nNeed any adjustments? I can:\n- Change timing or animations\n- Add\u002Fremove scenes\n- Update colors or fonts\n- Regenerate with different content\n```\n\n**Provide full file path** so user can easily access:\n```bash\n# Full path (resolved at runtime)\nrealpath \"$PROJECT_DIR\u002Foutput\u002F[video-name].mp4\"\n```\n\n**Optional: Open video automatically**:\n```bash\nopen \"$PROJECT_DIR\u002Foutput\u002F[video-name].mp4\"\n```\n(macOS only; skip on Linux\u002FWindows)\n\n---\n\n## Customization and Iteration\n\n**If user wants to make changes**:\n\n### Scenario 1: Content changes\n\"Change the title text in scene 1\"\n\n**Action**:\n- Edit Scene1.tsx\n- Update text content\n- Re-run render command\n- Deliver updated video\n\n### Scenario 2: Timing adjustments\n\"Make scene 2 longer\"\n\n**Action**:\n- Update durationInFrames in VideoComposition.tsx\n- Adjust subsequent scene timings (shift from values)\n- Re-render\n- Deliver updated video\n\n### Scenario 3: Visual changes\n\"Use different colors\"\n\n**Action**:\n- Update color values in scene components\n- Re-render\n- Deliver updated video\n\n### Scenario 4: Add\u002Fremove scenes\n\"Add an intro scene\"\n\n**Action**:\n- Create new Scene0.tsx\n- Update VideoComposition.tsx to include new Sequence\n- Shift timing of subsequent scenes\n- Re-render\n- Deliver updated video\n\n**Quick edit workflow**:\n```\nFor quick edits, you can:\n1. Modify files in $PROJECT_DIR\u002Fsrc\u002Fcompositions\u002F[video-name]\u002F\n2. Preview changes: npm run dev (opens Studio at localhost:3000)\n3. Re-render: npx remotion render src\u002Findex.ts [video-name] output\u002F[video-name].mp4\n\nLet me know what you'd like to change and I can update the code for you.\n```\n\n---\n\n## Error Handling & Recovery\n\n### Common Errors and Solutions\n\n**Error: \"Cannot find module 'remotion'\"**\n- **Cause**: Dependencies not installed\n- **Solution**: Re-run environment setup\n- **Command**: `cd \"$PROJECT_DIR\" && npm install`\n\n**Error: \"Composition not found\"**\n- **Cause**: Root.tsx not updated with new composition\n- **Solution**: Verify Root.tsx has correct import and Composition entry\n- **Fix**: Regenerate Root.tsx\n\n**Error: \"staticFile: File not found\"**\n- **Cause**: Asset doesn't exist at specified path\n- **Solution**: Verify asset exists in public\u002Fassets\u002F\n- **Command**: `ls \"$PROJECT_DIR\u002Fpublic\u002Fassets\u002F\"`\n\n**Error: \"FFmpeg exited with code 1\"**\n- **Cause**: FFmpeg error during encoding\n- **Solution**: Check FFmpeg installation, try different codec\n- **Command**: `ffmpeg -version`\n\n**Error: \"JavaScript heap out of memory\"**\n- **Cause**: Insufficient memory for rendering\n- **Solution**: Increase Node.js memory limit\n- **Command**: `export NODE_OPTIONS=\"--max-old-space-size=4096\"`\n\n**Error: TypeScript compilation errors**\n- **Cause**: Invalid TypeScript syntax in generated code\n- **Solution**: Fix syntax errors, ensure proper imports\n- **Action**: Review and correct the specific component\n\n### Graceful Degradation\n\nIf something fails:\n1. **Identify the issue**: Parse error message\n2. **Attempt fix**: Correct the specific problem\n3. **Retry**: Re-run the failed step\n4. **If still failing**: Provide clear error message and manual fix instructions\n5. **Fallback**: Offer to start over or skip problematic feature\n\n---\n\n## Best Practices\n\n### Code Quality\n\n**Generate clean code**:\n- Proper indentation and formatting\n- Meaningful variable names\n- Comments for complex logic\n- Consistent style throughout\n\n**Follow Remotion patterns**:\n- Use hooks correctly (useCurrentFrame, useVideoConfig)\n- Proper component structure\n- TypeScript types\n- Remotion-specific components\n\n**Performance considerations**:\n- Avoid heavy computations in render loop\n- Use memoization for expensive calculations\n- Optimize asset sizes\n- Efficient animation calculations\n\n### User Experience\n\n**Be proactive**:\n- Detect video intent automatically\n- Provide sensible defaults\n- Minimize required user input\n\n**Be transparent**:\n- Show what you're doing at each step\n- Explain rendering time\n- Report progress clearly\n\n**Be helpful**:\n- Offer preview before rendering\n- Provide file paths and commands\n- Suggest next steps\n- Enable easy customization\n\n**Be forgiving**:\n- Handle missing assets gracefully\n- Recover from errors\n- Offer alternatives when problems occur\n\n### Communication\n\n**Progress updates**:\n```\n✓ Environment ready\n✓ Storyboard created\n→ Generating code...\n```\n\n**Status indicators**:\n- ✓ Complete\n- → In progress\n- ⚠ Warning\n- ❌ Error\n- ℹ Information\n\n**Clear instructions**:\n- Provide exact commands\n- Show full file paths\n- Explain what each step does\n\n---\n\n## Integration with Other Skills\n\n### Uses environment-setup\n\nInvokes this skill first to ensure dependencies are installed.\n\n### Uses scene-planner\n\nInvokes this skill to create storyboard before code generation.\n\n### References remotion-best-practices\n\nApplies rules from this skill during code generation.\n\n### Reads templates\n\nReferences template files for structure and guidelines.\n\n---\n\n## Example Complete Workflow\n\n**User**: \"Create a 60-second explainer video about our AI writing assistant\"\n\n**Phase 1**: Environment check\n```\nChecking environment... ✓\nNode.js: v18.17.0 ✓\nFFmpeg: 6.0 ✓\nRemotion: 4.0.409 ✓\n```\n\n**Phase 2**: Requirements\n```\nI'll create an explainer video about your AI writing assistant.\n\nQuick questions:\n1. What's the main benefit users get? (e.g., \"Write 10x faster\", \"Never have writer's block\")\n2. Do you have a logo and any product screenshots?\n```\n\nUser provides: \"Main benefit is 'Write better content in half the time'. Yes, I have logo and 2 screenshots.\"\n\n**Phase 3**: Scene planning (internal - invokes scene-planner)\n\n**Phase 4**: Review\n```\nI've planned your explainer video:\n\nDuration: 60 seconds\nScenes: 6\n\n1. Hook (5s): \"Spending hours on every article?\"\n2. Problem (10s): Writer's block, slow writing, quality concerns\n3. Solution (8s): Introduce AI Writing Assistant\n4. How It Works (22s): 3 steps - Input topic, AI generates draft, Edit and publish\n5. Benefits (10s): Save time, improve quality, overcome blocks\n6. CTA (5s): \"Start writing better at [website].com\"\n\nAssets needed:\n- Logo ✓ (you have)\n- 2 product screenshots ✓ (you have)\n\nShall I proceed with generating the video?\n```\n\nUser: \"Yes, proceed\"\n\n**Phase 5**: Code generation\n```\nGenerating Remotion code...\n✓ Created VideoComposition.tsx\n✓ Created 6 scene components\n✓ Updated Root.tsx\n```\n\n**Phase 6**: Assets\n```\nPlease provide your assets:\n1. Logo file path:\n2. Screenshot 1 file path:\n3. Screenshot 2 file path:\n```\n\nUser provides paths. Assets copied.\n\n```\n✓ Integrated 3 assets\n```\n\n**Phase 7**: Preview\n```\n✓ Code generation complete!\n\nPreview available at: http:\u002F\u002Flocalhost:3000\n\nReview the video and let me know when ready to render final MP4.\n```\n\nUser reviews: \"Looks great, render it!\"\n\n**Phase 8**: Rendering\n```\nRendering video...\n[Progress bar]\n✓ Rendering complete! (took 2 minutes)\n```\n\n**Phase 9**: Delivery\n```\n🎬 Your video is ready!\n\n📁 $PROJECT_DIR\u002Foutput\u002Fai-writing-assistant-explainer.mp4\n⏱️  60 seconds\n📐 1920x1080 (Full HD)\n💾 15.3 MB\n🎨 6 scenes\n\nOpen video: open \"$PROJECT_DIR\u002Foutput\u002Fai-writing-assistant-explainer.mp4\"\n\nNeed changes? Let me know!\n```\n\n**Total time**: ~5 minutes (including rendering)\n\n---\n\n## Advanced Features (Future Enhancements)\n\nPotential future capabilities:\n\n**Voice-over generation**: Integrate text-to-speech\n**Subtitle generation**: Automatic captions\n**Multiple formats**: Render 16:9, 9:16, 1:1 simultaneously\n**Batch generation**: Create multiple videos from template\n**A\u002FB variants**: Generate multiple versions with variations\n**Direct upload**: Publish to YouTube\u002FInstagram via API\n\n---\n\n## Community-Driven Best Practices Integration\n\n> These practices are sourced from the most successful Remotion video toolkits in the community:\n> - remotion-dev\u002Ftemplate-prompt-to-motion-graphics (81 stars)\n> - digitalsamba\u002Fclaude-code-video-toolkit (40 stars)\n> - wshuyi\u002Fremotion-video-skill (70 stars)\n> - JJenglert1\u002Fremotion-claude-video (16 stars)\n\n### Constants-First Design (MANDATORY)\n\nAll generated code MUST place editable values at the top of each file:\n\n```typescript\n\u002F\u002F ============ EDITABLE CONSTANTS ============\nconst BRAND = {\n  primaryColor: '#2563EB',\n  accentColor: '#F97316',\n  backgroundColor: '#0F172A',\n  textColor: '#F8FAFC',\n};\n\nconst TYPOGRAPHY = {\n  headingFont: 'Inter',\n  bodyFont: 'Inter',\n  headingSize: 72,\n  bodySize: 28,\n  headingWeight: 700,\n  bodyWeight: 400,\n};\n\nconst CONTENT = {\n  title: 'Your Title Here',\n  subtitle: 'Your subtitle',\n  items: ['Point 1', 'Point 2', 'Point 3'],\n};\n\nconst TIMING = {\n  fps: 30,\n  sceneDurations: [150, 300, 240, 180],\n};\n\u002F\u002F ============================================\n```\n\n**Why**: Users can quickly customize videos by editing only the constant block, without understanding component internals. This is the single most impactful practice from the community.\n\n### Skill Detection and Injection\n\nBefore generating code, analyze the video requirements and inject only relevant Remotion best-practice rules:\n\n| Video Need | Rules to Reference |\n|------------|-------------------|\n| Text animations | `remotion-best-practices\u002Frules\u002Ftext-animations.md` |\n| Scene transitions | `remotion-best-practices\u002Frules\u002Ftransitions.md` |\n| Spring physics | `remotion-best-practices\u002Frules\u002Ftiming.md` |\n| Image handling | `remotion-best-practices\u002Frules\u002Fimages.md` |\n| Captions | `remotion-best-practices\u002Frules\u002Fdisplay-captions.md` |\n| Font loading | `remotion-best-practices\u002Frules\u002Fmeasuring-text.md` |\n| Parameters | `remotion-best-practices\u002Frules\u002Fparameters.md` |\n\nThis prevents context bloat while ensuring relevant expertise is applied.\n\n### Prompt Library Integration\n\nReference the prompt library at `${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002Fprompt-library\u002F` for:\n\n- **00-director-prompt.md**: System-level director prompt (inject for every video)\n- **01-product-launch.md**: Product launch \u002F feature announcement videos\n- **02-developer-tool-promo.md**: Open source \u002F developer tool promotions\n- **03-data-ranking.md**: Data charts and ranking animations\n- **04-kinetic-typography.md**: Quote and kinetic text videos\n- **05-app-walkthrough.md**: App UI demonstrations\n- **06-before-after.md**: Before vs After comparisons\n- **07-release-announcement.md**: Changelog \u002F version release videos\n- **08-thread-summary.md**: Thread \u002F post summary videos\n- **09-polish-prompts.md**: Post-generation quality enhancement\n\n### Iterative Quality Enhancement\n\nAfter initial code generation, apply a structured polish process:\n\n**Round 1: Structure** — Timeline logic, reading time, holds\n**Round 2: Visual** — Design system unity (fonts, colors, spacing)\n**Round 3: Animation** — Spring physics, stagger timing, background motion\n**Round 4: Detail** — Shadows, safe zones, contrast ratios\n\nReference `${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002Fprompt-library\u002F09-polish-prompts.md` for specific polish instructions.\n\n### Anti-Pattern Prevention\n\nDuring code generation, actively avoid these documented anti-patterns:\n\n**Text Animation Anti-Patterns**:\n- ❌ Per-character opacity for typewriter effect → ✅ Use `text.slice(0, n)`\n- ❌ Abrupt cursor blink (Math.round) → ✅ Smooth interpolated opacity\n- ❌ Word carousel without fixed width → ✅ Measure longest word, set fixed container\n\n**Transition Anti-Patterns**:\n- ❌ Hard cuts between scenes → ✅ Always crossfade (15-25 frames)\n- ❌ Transition duration > 45 frames → ✅ Keep transitions 15-25 frames\n\n**Animation Anti-Patterns**:\n- ❌ CSS transition\u002Fanimation → ✅ useCurrentFrame() + interpolate\u002Fspring\n- ❌ Linear easing for everything → ✅ spring() for key actions, linear only for constant motion\n- ❌ interpolate without clamp → ✅ Always add extrapolateLeft\u002FRight: 'clamp'\n\n**Resource Anti-Patterns**:\n- ❌ HTML `\u003Cimg>` tag → ✅ Remotion `\u003CImg>` component\n- ❌ Hardcoded file paths → ✅ `staticFile(\"assets\u002Ffile.png\")`\n- ❌ Spring config inline → ✅ Cache as constants\n\n### Reusable Animation Utilities\n\nGenerate these utility functions at the top of the composition or in a shared utils file:\n\n```typescript\n\u002F\u002F Fade + slide up (most common entrance)\nconst fadeSlideUp = (frame: number, start: number, duration = 20) => ({\n  opacity: interpolate(frame, [start, start + duration], [0, 1], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  }),\n  transform: `translateY(${interpolate(frame, [start, start + duration + 5], [30, 0], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  })}px)`,\n});\n\n\u002F\u002F Staggered list item reveal\nconst staggerItem = (frame: number, index: number, gap = 15) => ({\n  opacity: interpolate(frame, [index * gap, index * gap + 20], [0, 1], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  }),\n  transform: `translateX(${interpolate(frame, [index * gap, index * gap + 25], [-40, 0], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  })}px)`,\n});\n\n\u002F\u002F Typewriter text reveal\nconst typewriter = (frame: number, text: string, speed = 2) =>\n  text.slice(0, Math.min(Math.floor(frame \u002F speed), text.length));\n\n\u002F\u002F Count-up number animation\nconst countUp = (frame: number, target: number, start: number, duration: number) =>\n  Math.floor(target * interpolate(frame, [start, start + duration], [0, 1], {\n    extrapolateLeft: 'clamp', extrapolateRight: 'clamp',\n  }));\n```\n\n### Font Loading Best Practice\n\nAlways use `@remotion\u002Fgoogle-fonts` for font loading:\n\n```typescript\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FInter\";\nconst { fontFamily } = loadFont();\n\n\u002F\u002F Then use in styles:\nstyle={{ fontFamily }}\n```\n\nFor code\u002Fterminal scenes:\n```typescript\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FJetBrainsMono\";\nconst { fontFamily: monoFont } = loadFont();\n```\n\n---\n\n## Expanded Video Type Support\n\nBeyond the 4 core types (explainer, product demo, social media, presentation), this skill supports 10 additional high-impact video styles, each with a full **structural template** (`${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002F`) AND a **prompt library entry** (`${CODEBUDDY_PLUGIN_ROOT}\u002Ftemplates\u002Fprompt-library\u002F`):\n\n| Video Type | Template | Prompt Library | Duration |\n|---|---|---|---|\n| Product Launch | `templates\u002Fproduct-launch.md` | `prompt-library\u002F01-product-launch.md` | 10-15s |\n| Open Source Promo | `templates\u002Fopen-source-promo.md` | `prompt-library\u002F02-developer-tool-promo.md` | 15-30s |\n| Data Ranking | `templates\u002Fdata-ranking.md` | `prompt-library\u002F03-data-ranking.md` | 15-30s |\n| Kinetic Typography | `templates\u002Fkinetic-typography.md` | `prompt-library\u002F04-kinetic-typography.md` | 15-60s |\n| App Walkthrough | `templates\u002Fapp-walkthrough.md` | `prompt-library\u002F05-app-walkthrough.md` | 30-60s |\n| Before\u002FAfter | `templates\u002Fbefore-after.md` | `prompt-library\u002F06-before-after.md` | 10-20s |\n| Release Announcement | `templates\u002Frelease-announcement.md` | `prompt-library\u002F07-release-announcement.md` | 15-30s |\n| Thread Summary | `templates\u002Fthread-summary.md` | `prompt-library\u002F08-thread-summary.md` | 20-45s |\n| Map Route | `templates\u002Fmap-route.md` | — | 15-30s |\n| Music Visualization | `templates\u002Fmusic-visualization.md` | — | Matches audio |\n\n**How to use**: For each extended type, read BOTH the structural template (for scene breakdown, layout, animation code patterns) AND the prompt library entry (for user-facing prompt format, Constants-First code skeleton). The template provides the \"how\", the prompt library provides the \"what to ask\".\n\n---\n\nThis skill represents the complete orchestration layer that makes video generation seamless and automated for users. By coordinating environment setup, storyboarding, code generation, and rendering — and applying community-proven best practices like Constants-First Design, skill injection, and structured polish rounds — it transforms user ideas into production-ready, visually polished videos with minimal manual intervention.\n",{"name":5,"description":7},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Business-商业应用\u002FYYC3-Business-商业应用-acc-marketplace\u002Fplugins\u002Fremotion-video-generator\u002Fskills\u002Fvideo-generator",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill \"Video Generator\"",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill \"Video Generator\"",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill \"Video Generator\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Business-商业应用\u002FYYC3-Business-商业应用-acc-marketplace\u002Fplugins\u002Fremotion-video-generator\u002Fskills\u002Fvideo-generator\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]