Skills

Skill 1 of 13

Remotion Best Practices

Router for all Remotion skills

2 minutes · 519 words · 18 sections

Install

$ npx skills add remotion-dev/skills --skill remotion-best-practices

$ npx skills add remotion-dev/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Preserve user changes

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.

Creating a video

If the user asks to make, create, or build a new video or composition, load Create a new Remotion video (opens in a new tab), whether or not a Remotion project already exists.

New project setup

If no Remotion project currently exists, load Create a new Remotion project (opens in a new tab)

React Markup Best Practices

If you are writing Remotion React Markup, load Remotion Markup Best Practices (opens in a new tab)

Maps

For static maps, animated routes and markers, geographic explainers, Mapbox, MapLibre, MapTiler, GeoJSON, or 3D geographic flyovers, load Remotion Maps (opens in a new tab).

Multimedia

For achieving multimedia tasks in the browser, such as trimming, cropping videos, or getting metadata from them, load Remotion Multimedia (opens in a new tab)

Improving Interactivity

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 (opens in a new tab)

If the user asks to “make” a video, “create” a video, etc. Don’t render the video by default unless they are very explicit. They want to instead see an interactive preview. As soon as the project can run, start Studio and open the preview in the browser before building or editing the composition. Keep it open while you work so the user can watch progress and steer.

If you are using Cursor

Run Studio without --no-open so it opens the browser automatically:

npx remotion studio

If you are using another agent client with an in-app browser

You can use the command above to let Studio open the browser, or run:

npx remotion studio --no-open

This will start a long-running process and print the server URL for the preview.
If the server is already started, it will print the URL. If you use --no-open, open the exact printed URL in the 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. You can visit a specific composition by navigating to /[composition-id], for example http://localhost:3000/MapAnimation.

:::note The Studio supports WebMCP tools. :::

If you do not have an in-app browser

This will open the Studio in the browser or refocus it if it is already open.

npx remotion studio

More options

To launch a project in Remotion Studio, open its exact local URL, or configure Studio CLI flags, load Remotion Studio (opens in a new tab).

Render the video

Only render if the user is very explicit in asking for it.
E.g. “Render the video”, “Export”, “Give me the MP4”.

The preview also has a more intuitive rendering interface, so consider using it instead of the command line for rendering.

npx remotion render

For more options, see Rendering (opens in a new tab).

For advanced rendering beyond simple npx remotion render, see: Rendering Best Practices (opens in a new tab)

Captions

When working with Captions, load Remotion Captions (opens in a new tab).

Creating a SaaS, automation or application

Use the Remotion SaaS skill (opens in a new tab) 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.

Looking up Remotion APIs and documentation

To find and read current Remotion documentation, load Remotion Docs (opens in a new tab).

Licensing

For Remotion license information, FAQs, terms, or buying a license, load Remotion License (opens in a new tab).

Upgrading

To upgrade Remotion, related packages, compatible Mediabunny packages, and installed Remotion Agent Skills, load Remotion Upgrade (opens in a new tab).

Colophon for this issue

Colophon

How this issue was made

Source: github.com/remotion-dev/skills, branch main, last pushed 5 November 2026.
Licence: All rights reserved — view on GitHub — with no detectable licence, this issue links rather than republishes: the skills are omitted from the agent manifest and from the whole-book markdown.
Discovery: 13 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.
Issue colours: Resolved from a curated brand profile — hue 254°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.
Heading repairs: None needed in this skill: the outline was already valid.
Spec compliance: Every skill satisfies the Agent Skills specification’s frontmatter rules.
Images: Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.
Signal: Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.
Agent surfaces: The whole issue is available as one markdown document at /remotion-dev/skills.md, and each skill at its own .md URL.
Publication: Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.