Route Remotion tasks to the relevant specialist guides, from creating videos and projects to captions, maps, and rendering. It also guides Studio preview setup, package upgrades, and troubleshooting when working inside Codex.
Router for all Remotion skills
Review the instructions the agent will receive before you install.
Users may make edits in the code outside of the conversation.
If you detect a surprising change made in the meanwhile, don't overwrite it, assume it was intentional or ask for confirmation.
If the user asks to make, create, or build a new video or composition, load Create a new Remotion video, whether or not a Remotion project already exists.
If no Remotion project currently exists, load Create a new Remotion project
If you are writing Remotion React Markup, load Remotion Markup Best Practices
For static maps, animated routes and markers, geographic explainers, Mapbox, MapLibre, MapTiler, GeoJSON, or 3D geographic flyovers, load Remotion Maps.
For achieving multimedia tasks in the browser, such as trimming, cropping videos, or getting metadata from them, load Remotion Multimedia
By structuring the Remotion markup well, we can allow users to interactively change things in the Studio and write back to code. If relevant: Interactivity Best Practices
For advanced rendering beyond simple npx remotion render, see: Rendering Best Practices
When creating or editing a video, start Studio and open its preview as soon as the project can run, before building the composition. Keep it open while you work so the user can see changes and steer.
To launch a project in Remotion Studio, open its exact local URL, or configure Studio CLI flags, load Remotion Studio.
When working with Captions, load Remotion Captions.
Use the Remotion SaaS skill for knowledge about Remotion-powered SaaS apps, such as <Player>, rendering on Lambda, Vercel, Cloudflare, via Express.js, client-side rendering, or for finding the right SaaS template.
To find and read current Remotion documentation, load Remotion Docs.
To upgrade Remotion, related packages, compatible Mediabunny packages, and installed Remotion Agent Skills, load Remotion Upgrade.
When running inside Codex, first try starting the Remotion Studio without opening the system browser:
npx remotion studio --no-open
Open the exact printed URL in the Codex in-app browser and verify that Studio loads. Once a composition exists, verify that its video preview loads. If you cannot open it there, run Studio without --no-open.
Only if that fails with file watcher limits such as EMFILE: too many open files, watch, retry with polling and without opening a browser from Codex:
npx remotion studio --no-open --webpack-poll 1000
After retrying, open the exact printed URL in the Codex in-app browser and verify that Studio loads. Once a composition exists, verify that its video preview loads. If you cannot open it there, retry without --no-open.
If Studio still fails to start from Codex, ask the user to start it manually from their macOS Terminal and then continue using the already-running Studio. Sandbox errors while launching Chromium from Codex are likely caused by the Codex/macOS sandbox rather than the Remotion project.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.