agentleFS
BAKUGOS1BAKUGOS1/SkilledAgents-Toolkit/skills/codex/remotion/SKILL.md

remotion

Skill0 starsChanged 5 months agoMITView on GitHub

Generate walkthrough videos from Stitch projects using Remotion with smooth transitions, zooming, and text overlays

  • Installs packages

37 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

Show its rules and text

We split this skill into the rules it gives an agent

37 rules. 0 are common, 20 are distinctive, and 17 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 20

    Distinctive

    This author's own choices. Worth a look.

  • 17

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run list_tools to identify available MCP servers and their prefixes:

    line 37
  2. Very specific:

    Stitch MCP: Look for stitch: or mcp_stitch: prefix

    line 38
  3. Very specific:

    Remotion MCP: Look for remotion: or mcp_remotion: prefix

    line 39
  4. Very specific:

    Call [stitch_prefix]:list_projects with filter: "view=owned"

    line 44
  5. Very specific:

    Call [stitch_prefix]:list_screens with the project ID (numeric only)

    line 49
  6. Very specific:

    Call [stitch_prefix]:get_screen with projectId and screenId

    line 55
  7. Very specific:

    Use web_fetch or Bash with curl to download screenshots

    line 63
  8. Very specific:

    Look for remotion.config.ts or package.json with Remotion dependencies

    line 70
  9. Distinctive:

    If exists, use the existing project structure

    line 71
  10. Distinctive:

    Create a modular Remotion composition with these components:

    line 90
  11. Very specific:

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

    line 109
  12. Very specific:

    Use spring() animation for smooth zoom

    line 122
  13. Distinctive:

    Add contextual information using Remotion's text rendering:

    line 127
  14. Very specific:

    Create a manifest file (screens.json):

    line 142
  15. Distinctive:

    Create the video components following Remotion best practices:

    line 172
  16. Very specific:

    Use useCurrentFrame() and spring() for animations

    line 175
  17. Distinctive:

    Add text overlays with proper timing

    line 177
  18. Very specific:

    Use resources/screen-slide-template.tsx as starting point

    line 191
  19. Very specific:

    Follow resources/composition-checklist.md for completeness

    line 192
  20. Distinctive:

    Ensure each screen has appropriate display duration

    line 205
  21. Distinctive:

    Verify transitions are smooth

    line 206
  22. Distinctive:

    Check text overlay timing

    line 207
  23. Distinctive:

    Ensure text is readable at all times

    line 212
  24. Very specific:

    Call [remotion_prefix]:render with composition details

    line 222
  25. Distinctive:

    Add narration to the walkthrough:

    line 263
  26. Distinctive:

    Use text-to-speech or record audio

    line 266
  27. Very specific:

    Import audio into Remotion with <Audio> component

    line 267
  28. Distinctive:

    Add to composition as timed text overlays

    line 277
  29. Distinctive:

    Maintain aspect ratio: Use actual Stitch screen dimensions or scale proportionally

    line 353
  30. Distinctive:

    Consistent timing: Keep screen display duration consistent unless emphasizing specific screens

    line 354
  31. Distinctive:

    Readable text: Ensure sufficient contrast.

    line 355
  32. Distinctive:

    Smooth transitions: Use spring animations for natural motion.

    line 356
  33. Distinctive:

    Preview thoroughly: Always preview in Remotion Studio before final render

    line 357
  34. Very specific:

    Create screens.json manifest with screen metadata

    line 372
  35. Distinctive:

    Use manifest files: Keep screen data organized in JSON for easy updates

    line 382
  36. Distinctive:

    Preview frequently: Use Remotion Studio to catch issues early

    line 383
  37. Distinctive:

    Consider accessibility: Add captions; ensure text is readable.

    line 384

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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/ 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

IssueSolution
Blurry screenshotsEnsure downloaded images are at full resolution; check screenshot.downloadUrl quality settings
Misaligned textVerify screen dimensions match composition size; adjust text positioning based on actual screen size
Choppy animationsIncrease frame rate to 60fps; use proper spring configurations with appropriate damping
Remotion build failsCheck Node version compatibility; ensure all dependencies are installed; review Remotion docs
Timing feels offAdjust 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
  2. Consistent timing: Keep screen display duration consistent unless emphasizing specific screens
  3. Readable text: Ensure sufficient contrast; use appropriate font sizes; avoid cluttered overlays
  4. Smooth transitions: Use spring animations for natural motion; avoid jarring cuts
  5. Preview thoroughly: Always preview in Remotion Studio before final render
  6. Optimize assets: Compress images appropriately; use efficient formats (PNG for UI, JPG for photos)

Example Usage

User prompt:

Look up the screens in my Stitch project "Calculator App" and build a remotion video 
that shows a walkthrough of the screens.

Agent workflow:

  1. List Stitch projects → Find "Calculator App" → Extract project ID
  2. List screens in project → Identify all screens (Home, History, Settings)
  3. Download screenshots for each screen → Save to assets/screens/
  4. Create screens.json manifest with screen metadata
  5. Generate Remotion components (ScreenSlide.tsx, WalkthroughComposition.tsx)
  6. Preview in Remotion Studio → Refine timing and transitions
  7. Render final video → calculator-walkthrough.mp4
  8. Report completion with video preview link

Tips for Success

  • Start simple: Begin with basic fade transitions before adding complex animations
  • Follow Remotion patterns: Leverage Remotion's official skills and documentation
  • Use manifest files: Keep screen data organized in JSON for easy updates
  • Preview frequently: Use Remotion Studio to catch issues early
  • Consider accessibility: Add captions; ensure text is readable; use clear visuals
  • Optimize for platform: Match video dimensions to target platform (YouTube, social media, etc.)

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.