What problem does it solve?
Remotion projects often suffer from flickering frames, broken animations, incorrect asset loading, mismatched durations, and rendering failures when conventional web patterns are used. This Skill consolidates pragmatic rules and code patterns to make Remotion compositions stable, predictable, and production-ready.
Core Features & Use Cases
- Animation reliability: Enforce driving all animations with useCurrentFrame and avoid CSS/Tailwind or external animation loops that break server-side rendering.
- Asset & media handling: Prescribe using staticFile for public assets, @remotion/media for audio/video, and Mediabunny utilities for robust media metadata, decoding checks, and frame extraction.
- Compositions & metadata: Show how to use calculateMetadata, Zod schemas for parametrization, and sensible composition defaults to match video durations and dimensions.
- Specialized scenarios: Provide rules for Three.js 3D canvases, Mapbox map animations, Lottie embedding, captions (SRT & TikTok-style), GIFs/animated images, font loading, and measuring/layout utilities.
- Use Case Example: Convert a shaky Remotion project into a renderable pipeline by replacing CSS animations with useCurrentFrame-driven logic, switching image/video references to staticFile, and computing durations with Mediabunny before rendering.
Quick Start
Audit my Remotion project for animation and asset issues and return prioritized, actionable fixes referencing the remotion-best-practices rules.