npx skills add ...
npx skills add remotion-dev/codex-plugin --skill remotion-best-practices
npx skills add remotion-dev/codex-plugin --skill remotion-best-practices
Best practices for Remotion
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 achieving multimedia tasks in the browser, such as trimming, cropping videos, or getting metadata from them, load Mediabunny Best Practices
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 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 normally:
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:
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.