remotion

google-labs-code/stitch-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/google-labs-code/stitch-skills --skill remotion
0 commentsdiscussion
summary

Create professional walkthrough videos from Stitch app designs using Remotion with smooth transitions and text overlays.

  • Retrieves screens from Stitch projects and orchestrates them into Remotion video compositions with zoom effects, fade transitions, and contextual text overlays
  • Supports modular component architecture with ScreenSlide and WalkthroughComposition components, plus advanced features like interactive hotspots and voiceover integration
  • Generates screen manifests, download
skill.md

Stitch to Remotion Walkthrough Videos

You are a video production specialist focused on creating engaging walkthrough videos from app designs. You combine Stitch's screen retrieval capabilities with Remotion's programmatic video generation to produce smooth, professional presentations.

Overview

This skill enables you to create walkthrough videos that showcase app screens with professional transitions, zoom effects, and contextual text overlays. The workflow retrieves screens from Stitch projects and orchestrates them into a Remotion video composition.

Prerequisites

Required:

  • Access to the Stitch MCP Server
  • Access to the Remotion MCP Server (or Remotion CLI)
  • Node.js and npm installed
  • A Stitch project with designed screens

Recommended:

  • Familiarity with Remotion's video capabilities
  • Understanding of React components (Remotion uses React)

Retrieval and Networking

Step 1: Discover Available MCP Servers

Run list_tools to identify available MCP servers and their prefixes:

  • Stitch MCP: Look for stitch: or mcp_stitch: prefix
  • Remotion MCP: Look for remotion: or mcp_remotion: prefix

Step 2: Retrieve Stitch Project Information

  1. Project lookup (if Project ID is not provided):

    • Call [stitch_prefix]:list_projects with filter: "view=owned"
    • Identify target project by title (e.g., "Calculator App")
    • Extract Project ID from name field (e.g., projects/13534454087919359824)
  2. Screen retrieval:

    • Call [stitch_prefix]:list_screens with the project ID (numeric only)
    • Review screen titles to identify all screens for the walkthrough
    • Extract Screen IDs from each screen's name field
  3. Screen metadata fetch: For each screen:

    • Call [stitch_prefix]:get_screen with projectId and screenId
    • Retrieve:
      • screenshot.downloadUrl — Visual asset for the video
      • htmlCode.downloadUrl — Optional: for extracting text/content
      • width, height — Screen dimensions for proper scaling
      • Screen title and description for text overlays
  4. Asset download:

    • Use web_fetch or Bash with curl to download screenshots
    • Save to a staging directory: assets/screens/{screen-name}.png
    • Organize assets in order of the intended walkthrough flow

Step 3: Set Up Remotion Project

  1. Check for existing Remotion project:

    • Look for remotion.config.ts or package.json with Remotion dependencies
    • If exists, use the existing project structure
  2. Create new Remotion project (if needed):

    npm create video@latest -- --blank
    
    • Choose TypeScript template
    • Set up in a dedicated video/ directory
  3. Install dependencies:

    cd video
    npm install @remotion/transitions @remotion/animated-emoji
    

Video Composition Strategy

Architecture

Create a modular Remotion composition with these components:

  1. ScreenSlide.tsx — Individual screen display component

    • Props: imageSrc, title, description, width, height
    • Features: Zoom-in animation, fade transitions
    • Duration: Configurable (default 3-5 seconds per screen)
  2. WalkthroughComposition.tsx — Main video composition

    • Sequences multiple ScreenSlide components
    • Handles transitions between screens
    • Adds text overlays and annotations
  3. config.ts — Video configuration

    • Frame rate (default: 30 fps)
    • Video dimensions (match Stitch screen dimensions or scale appropriately)
    • Total duration calculation

Transition Effects

Use Remotion's @remotion/transitions for professional effects:

  • Fade: Smooth cross-fade between screens

    import {fade} from '@remotion/transitions/fade';
    
  • Slide: Directional slide transitions

    import {slide} from '@remotion/transitions/slide';
    
  • Zoom: Zoom in/out effects for emphasis

    • Use spring() animation for smooth zoom
    • Apply to important UI elements

Text Overlays

Add contextual information using Remotion's text rendering:

  1. Screen titles: Display at the top or bottom of each frame
  2. Feature callouts: Highlight specific UI elements with animated pointers
  3. Descriptions: Fade in descriptive text for each screen
  4. Progress indicator: Show current screen position in walkthrough

Execution Steps

Step 1: Gather Screen Assets

  1. Identify target Stitch project
  2. List all screens in the project
  3. Download screenshots for each screen
  4. Organize in order of walkthrough flow
  5. Create a manifest file (screens.json):
{
  "projectName": "Calculator App",
  "screens": [
    {
      "id": "1",
      "title": "Home Screen",
      "description": "Main calculator interface with number pad",
      "imagePath": "assets/screens/home.png",
      "width": 1200,
      "height": 800,
      "duration": 4
    },
    {
      "id": "2",
      "title": "History View",
      "description": "View of previous calculations",
      "imagePath": "assets/screens/history.png",
      "width": 1200,
      "height": 800,
      "duration": 3
    }
  ]
}

Step 2: Generate Remotion Components

Create the video components following Remotion best practices:

  1. Create ScreenSlide.tsx:

    • Use useCurrentFrame() and spring() for animations
    • Implement zoom and fade effects
    • Add text overlays with proper timing
  2. Create WalkthroughComposition.tsx:

    • Import screen manifest
    • Sequence screens with <Sequence> components
    • Apply transitions between screens
    • Calculate proper timing and offsets
  3. Update remotion.config.ts:

    • Set composition ID
    • Configure video dimensions
    • Set frame rate and duration

Reference Resources:

  • Use resources/screen-slide-template.tsx as starting point
  • Follow resources/composition-checklist.md for completeness
  • Review examples in examples/walkthrough/ directory

Step 3: Preview and Refine

  1. Start Remotion Studio:

    npm run dev
    
    • Opens browser-based preview
    • Allows real-time editing and refinement
  2. Adjust timing:

    • Ensure each screen has appropriate display duration
    • Verify transitions are smooth
    • Check text overlay timing
  3. Fine-tune animations:

    • Adjust spring configurations for zoom effects
    • Modify easing functions for transitions
    • Ensure text is readable at all times

Step 4: Render Video

  1. Render using Remotion CLI:

    npx remotion render WalkthroughComposition output.mp4
    
  2. Alternative: Use Remotion MCP (if available):

    • Call [remotion_prefix]:render with composition details
    • Specify output format (MP4, WebM, etc.)
  3. Optimization options:

    • Set quality level (--quality)
    • Configure codec (--codec h264 or h265)
    • Enable parallel rendering (--concurrency)

Advanced Features

Interactive Hotspots

Highlight clickable elements or important features:

import {interpolate, useCurrentFrame} from 'remotion';

const Hotspot = ({x, y, label}) => {
  const frame = useCurrentFrame();
  const scale = spring({
    frame,
    fps: 30,
    config: {damping: 10, stiffness: 100}
  });
  
  return (
    <div style={{
      position: 'absolute',
      left: x,
      top: y,
      transform: `scale(${scale})`
    }}>
      <div className="pulse-ring" />
      <span>{label}</span>
    </div>
  );
};

Voiceover Integration

Add narration to the walkthrough:

  1. Generate voiceover script from screen descriptions
  2. Use text-to-speech or record audio
  3. Import audio into Remotion with <Audio> component
  4. Sync screen timing with voiceover pacing

Dynamic Text Extraction

Extract text from Stitch HTML code for automatic annotations:

  1. Download htmlCode.downloadUrl for each screen
  2. Parse HTML to extract key text elements (headings, buttons, labels)
  3. Generate automatic callouts for important UI elements
  4. Add to composition as timed text overlays

File Structure

project/
├── video/                      # Remotion project directory
│   ├── src/
│   │   ├── WalkthroughComposition.tsx
│   │   ├── ScreenSlide.tsx
│   │   ├── components/
│   │   │   ├── Hotspot.tsx
│   │   │   └── TextOverlay.tsx
│   │   └── Root.tsx
│   ├── public/
│   │   └── assets/
│   │       └── screens/        # Downloaded Stitch screenshots
│   │           ├── home.png
│   │           └── history.png
│   ├── remotion.config.ts
│   └── package.json
├── screens.json                # Screen manifest
└── output.mp4                  # Rendered video

Integration with Remotion Skills

Remotion maintains its own Agent Skills that define best practices. Review these for advanced techniques:

Key Remotion skills to leverage:

  • Animation timing and easing
  • Composition architecture patterns
  • Performance optimization
  • Audio synchronization

Common Patterns

Pattern 1: Simple Slide Show

Basic walkthrough with fade transitions:

  • 3-5 seconds per screen
  • Cross-fade transitions
  • Bottom text overlay with screen title
  • Progress bar at top

Pattern 2: Feature Highlight

Focus on specific UI elements:

  • Zoom into specific regions
  • Animated circles/arrows pointing to features
  • Slow-motion emphasis on key interactions
  • Side-by-side before/after comparisons

Pattern 3: User Flow

Show step-by-step user journey:

  • Sequential screen flow with directional slides
  • Numbered steps overlay
  • Highlight user actions (clicks, taps)
  • Connect screens with animated paths

Troubleshooting

Issue Solution
Blurry screenshots Ensure downloaded images are at full resolution; check screenshot.downloadUrl quality settings
Misaligned text Verify screen dimensions match composition size; adjust text positioning based on actual screen size
Choppy animations Increase frame rate to 60fps; use proper spring configurations with appropriate damping
Remotion build fails Check Node version compatibility; ensure all dependencies are installed; review Remotion docs
Timing feels off Adjust duration per screen in manifest; preview in Remotion Studio; test with actual users

Best Practices

  1. Maintain aspect ratio: Use actual Stitch screen dimensions or scale proportionally
how to use remotion

How to use remotion on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add remotion
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/google-labs-code/stitch-skills --skill remotion

The skills CLI fetches remotion from GitHub repository google-labs-code/stitch-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/remotion

Reload or restart Cursor to activate remotion. Access the skill through slash commands (e.g., /remotion) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.628 reviews
  • Camila Ndlovu· Dec 28, 2024

    Useful defaults in remotion — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chaitanya Patil· Dec 24, 2024

    I recommend remotion for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Chinedu Singh· Dec 4, 2024

    remotion has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Chinedu Ghosh· Nov 23, 2024

    remotion reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ishan Park· Nov 19, 2024

    I recommend remotion for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Piyush G· Nov 15, 2024

    Useful defaults in remotion — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aditi White· Oct 14, 2024

    I recommend remotion for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kabir Singh· Oct 10, 2024

    remotion reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Shikha Mishra· Oct 6, 2024

    remotion has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hana Martinez· Sep 21, 2024

    remotion fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 28

1 / 3