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
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- soilmass/motion-design-agenttheir own version, first seen Nov 8, 2026
- OpenMontageInc/OpenMontagetheir own version, first seen Nov 8, 2026
- digitalsamba/claude-code-video-toolkittheir own version, first seen Nov 8, 2026
- calesthio/OpenMontagetheir own version, first seen Nov 8, 2026
- delorenj/skillsedited, first seen Nov 7, 2026
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.
aaronjmarsSkillaeon-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
aaronjmarsSkillauto-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
Other versions37 projects use a version of this.
Word for word · 1
- jratlee/FDI★ 0100% same
Edited · 5
- diodeme/Gold-Band★ 164100% same
- delorenj/skills★ 1799% same
- klauswg/sasuke★ 17100% same
- jaron-goh-centr/claude-skills★ 0100% same
- minhtrung0110/wp-test-tool★ 0100% same
Wrote their own version · 31
- calesthio/OpenMontage★ 78ksame name
- OpenMontageInc/OpenMontage★ 78ksame name
- vercel-labs/json-render★ 19ksame name
- digitalsamba/claude-code-video-toolkit★ 2.5ksame name
- aaronjmars/aeon★ 789same name
- aeonfun/aeon★ 789same name
- dracohu2025-cloud/draco-skills-collection★ 227same name
- TheBeardedBearSAS/claude-craft★ 108same name
- realjaymes/marketingagentskills★ 68same name
- podo/design-agent-skills★ 32same name
21 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- find-skillsSkill
- notebooklmSkill
- stitch::code-to-designSkill
- design-mdSkill
- doc-coauthoringSkill
- enhance-promptSkill
- stitch::extract-design-mdSkill
- stitch::extract-static-htmlSkill
- frontend-designSkill
- stitch::generate-designSkill
- hatch-petSkill
- impeccableSkill
- internal-commsSkill
- karpathy-guidelinesSkill
- stitch::manage-design-systemSkill
- mcp-builderSkill
- product-engineering-auditorSkill
- react:componentsSkill
- shadcn-uiSkill
- stitch-loopSkill
- taste-designSkill
- design-taste-frontendSkill
- ui-ux-pro-maxSkill
- stitch::upload-to-stitchSkill
- webapp-testingSkill
- website-builder-setupSkill
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
- Very specific: line 37
Run list_tools to identify available MCP servers and their prefixes:
- Very specific: line 38
Stitch MCP: Look for stitch: or mcp_stitch: prefix
- Very specific: line 39
Remotion MCP: Look for remotion: or mcp_remotion: prefix
- Very specific: line 44
Call [stitch_prefix]:list_projects with filter: "view=owned"
- Very specific: line 49
Call [stitch_prefix]:list_screens with the project ID (numeric only)
- Very specific: line 55
Call [stitch_prefix]:get_screen with projectId and screenId
- Very specific: line 63
Use web_fetch or Bash with curl to download screenshots
- Very specific: line 70
Look for remotion.config.ts or package.json with Remotion dependencies
- Distinctive: line 71
If exists, use the existing project structure
- Distinctive: line 90
Create a modular Remotion composition with these components:
- Very specific: line 109
Use Remotion's @remotion/transitions for professional effects:
- Very specific: line 122
Use spring() animation for smooth zoom
- Distinctive: line 127
Add contextual information using Remotion's text rendering:
- Very specific: line 142
Create a manifest file (screens.json):
- Distinctive: line 172
Create the video components following Remotion best practices:
- Very specific: line 175
Use useCurrentFrame() and spring() for animations
- Distinctive: line 177
Add text overlays with proper timing
- Very specific: line 191
Use resources/screen-slide-template.tsx as starting point
- Very specific: line 192
Follow resources/composition-checklist.md for completeness
- Distinctive: line 205
Ensure each screen has appropriate display duration
- Distinctive: line 206
Verify transitions are smooth
- Distinctive: line 207
Check text overlay timing
- Distinctive: line 212
Ensure text is readable at all times
- Very specific: line 222
Call [remotion_prefix]:render with composition details
- Distinctive: line 263
Add narration to the walkthrough:
- Distinctive: line 266
Use text-to-speech or record audio
- Very specific: line 267
Import audio into Remotion with <Audio> component
- Distinctive: line 277
Add to composition as timed text overlays
- Distinctive: line 353
Maintain aspect ratio: Use actual Stitch screen dimensions or scale proportionally
- Distinctive: line 354
Consistent timing: Keep screen display duration consistent unless emphasizing specific screens
- Distinctive: line 355
Readable text: Ensure sufficient contrast.
- Distinctive: line 356
Smooth transitions: Use spring animations for natural motion.
- Distinctive: line 357
Preview thoroughly: Always preview in Remotion Studio before final render
- Very specific: line 372
Create screens.json manifest with screen metadata
- Distinctive: line 382
Use manifest files: Keep screen data organized in JSON for easy updates
- Distinctive: line 383
Preview frequently: Use Remotion Studio to catch issues early
- Distinctive: line 384
Consider accessibility: Add captions; ensure text is readable.
“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.
Files
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:ormcp_stitch:prefix - Remotion MCP: Look for
remotion:ormcp_remotion:prefix
Step 2: Retrieve Stitch Project Information
- Project lookup (if Project ID is not provided):
- Call
[stitch_prefix]:list_projectswithfilter: "view=owned" - Identify target project by title (e.g., "Calculator App")
- Extract Project ID from
namefield (e.g.,projects/13534454087919359824)
- Call
- Screen retrieval:
- Call
[stitch_prefix]:list_screenswith the project ID (numeric only) - Review screen titles to identify all screens for the walkthrough
- Extract Screen IDs from each screen's
namefield
- Call
- Screen metadata fetch:
For each screen:
- Call
[stitch_prefix]:get_screenwithprojectIdandscreenId - Retrieve:
screenshot.downloadUrl— Visual asset for the videohtmlCode.downloadUrl— Optional: for extracting text/contentwidth,height— Screen dimensions for proper scaling- Screen title and description for text overlays
- Call
- Asset download:
- Use
web_fetchorBashwithcurlto download screenshots - Save to a staging directory:
assets/screens/{screen-name}.png - Organize assets in order of the intended walkthrough flow
- Use
Step 3: Set Up Remotion Project
- Check for existing Remotion project:
- Look for
remotion.config.tsorpackage.jsonwith Remotion dependencies - If exists, use the existing project structure
- Look for
- Create new Remotion project (if needed):
npm create video@latest -- --blank- Choose TypeScript template
- Set up in a dedicated
video/directory
- Install dependencies:
cd video npm install @remotion/transitions @remotion/animated-emoji
Video Composition Strategy
Architecture
Create a modular Remotion composition with these components:
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)
- Props:
WalkthroughComposition.tsx— Main video composition- Sequences multiple
ScreenSlidecomponents - Handles transitions between screens
- Adds text overlays and annotations
- Sequences multiple
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
- Use
Text Overlays
Add contextual information using Remotion's text rendering:
- Screen titles: Display at the top or bottom of each frame
- Feature callouts: Highlight specific UI elements with animated pointers
- Descriptions: Fade in descriptive text for each screen
- Progress indicator: Show current screen position in walkthrough
Execution Steps
Step 1: Gather Screen Assets
- Identify target Stitch project
- List all screens in the project
- Download screenshots for each screen
- Organize in order of walkthrough flow
- 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:
- Create
ScreenSlide.tsx:- Use
useCurrentFrame()andspring()for animations - Implement zoom and fade effects
- Add text overlays with proper timing
- Use
- Create
WalkthroughComposition.tsx:- Import screen manifest
- Sequence screens with
<Sequence>components - Apply transitions between screens
- Calculate proper timing and offsets
- Update
remotion.config.ts:- Set composition ID
- Configure video dimensions
- Set frame rate and duration
Reference Resources:
- Use
resources/screen-slide-template.tsxas starting point - Follow
resources/composition-checklist.mdfor completeness - Review examples in
examples/directory
Step 3: Preview and Refine
- Start Remotion Studio:
npm run dev- Opens browser-based preview
- Allows real-time editing and refinement
- Adjust timing:
- Ensure each screen has appropriate display duration
- Verify transitions are smooth
- Check text overlay timing
- 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
- Render using Remotion CLI:
npx remotion render WalkthroughComposition output.mp4 - Alternative: Use Remotion MCP (if available):
- Call
[remotion_prefix]:renderwith composition details - Specify output format (MP4, WebM, etc.)
- Call
- Optimization options:
- Set quality level (
--quality) - Configure codec (
--codec h264orh265) - Enable parallel rendering (
--concurrency)
- Set quality level (
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:
- Generate voiceover script from screen descriptions
- Use text-to-speech or record audio
- Import audio into Remotion with
<Audio>component - Sync screen timing with voiceover pacing
Dynamic Text Extraction
Extract text from Stitch HTML code for automatic annotations:
- Download
htmlCode.downloadUrlfor each screen - Parse HTML to extract key text elements (headings, buttons, labels)
- Generate automatic callouts for important UI elements
- 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 videoIntegration with Remotion Skills
Remotion maintains its own Agent Skills that define best practices. Review these for advanced techniques:
- Repository: https://github.com/remotion-dev/remotion/tree/main/packages/skills
- Installation:
npx skills add remotion-dev/skills
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
- Maintain aspect ratio: Use actual Stitch screen dimensions or scale proportionally
- Consistent timing: Keep screen display duration consistent unless emphasizing specific screens
- Readable text: Ensure sufficient contrast; use appropriate font sizes; avoid cluttered overlays
- Smooth transitions: Use spring animations for natural motion; avoid jarring cuts
- Preview thoroughly: Always preview in Remotion Studio before final render
- 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:
- List Stitch projects → Find "Calculator App" → Extract project ID
- List screens in project → Identify all screens (Home, History, Settings)
- Download screenshots for each screen → Save to
assets/screens/ - Create
screens.jsonmanifest with screen metadata - Generate Remotion components (
ScreenSlide.tsx,WalkthroughComposition.tsx) - Preview in Remotion Studio → Refine timing and transitions
- Render final video →
calculator-walkthrough.mp4 - 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
- Stitch Documentation: https://stitch.withgoogle.com/docs/
- Remotion Documentation: https://www.remotion.dev/docs/
- Remotion Skills: https://www.remotion.dev/docs/ai/skills
- Remotion MCP: https://www.remotion.dev/docs/ai/mcp
- Remotion Transitions: https://www.remotion.dev/docs/transitions
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
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.

