--- name: remotion-create description: Create a new Remotion video version: 4.0.535 title: remotion-create canonical_url: https://skilld.dev/gh/remotion-dev/skills/remotion-create last_updated: 2026-10-13T21:25:48.000Z --- > Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt) > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-create/agents/openai.yaml), [assets/remotion-icon.svg](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-create/assets/remotion-icon.svg), [tailwind.md](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-create/tailwind.md), [video-layout.md](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-create/video-layout.md). > > If the user asked to install this Skill, run `npx skilld install remotion-dev/skills/remotion-create`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/remotion-create`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/remotion-dev/skills/remotion-create) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/remotion-create`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/remotion-create --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/remotion-create --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. These are instructions for making a new Remotion project and composition. If this is not the next task, see Remotion Best Practices ## Scaffold a project If a project already exists, skip this. Ensure Node.js and Git is installed, and the current folder is appropriate for starting a new project. Inspect the current folder, including hidden files, before choosing where to scaffold. ### Empty folder If it is empty, or contains only disposable operating-system metadata such as `.DS_Store`, create the project directly in the current folder. Remove only those disposable metadata files first, since `create-video` rejects non-empty folders. Do not treat all hidden files as disposable: files such as `.env` and directories such as `.git` are meaningful contents. Scaffold in existing folder: ```bash npx create-video@latest --yes --blank --no-tailwind . npm i ``` ### Non-empty folder If the current folder contains meaningful contents and no project already exists, scaffold into a new subfolder. Replace `my-video` with a suitable project name. ```bash npx create-video@latest --yes --blank --no-tailwind my-video cd my-video npm i ``` ## Open the preview before building the video As soon as the project can run, open Remotion Studio in the browser before writing or changing the composition. For a new project, do this immediately after scaffolding and installing dependencies. For an existing project, do it before editing the video. Keep Studio running while you work so the user can see changes as they appear and steer the result. ## Designing a video Keep the scaffold and add React Markup. Follow Remotion React Markup Best Practices and [Video Layout Rules](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-create/video-layout.md) for video-first layout and text sizing guidance. Before writing the root that registers `` or `` elements, follow Compositions and stills. ## Is this a timeline of clips? If the video arranges multiple video or audio clips on a timeline, follow Video editing before writing the timeline. Give every clip that should be edited independently its own authored JSX node. ## Is this a multi-scene video? If this is a video with multiple subsequent scenes, follow guidance at Multi-scene videos. ## Interactivity Best Practices By structuring the React Markup following Remotion Interactivity Best Practices, you allow the user to make edits in the Studio which write back to code. ## TailwindCSS If Tailwind is requested, see [tailwind.md](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-create/tailwind.md) for using TailwindCSS in Remotion. ## Follow-up The video creation process has finished. For follow-up prompts, use Remotion Best Practices