agentleFS
muzimu217muzimu217/ui-design-agent-kit/.agents/skills/remotion-create/SKILL.md

remotion-create

Skill23 starsChanged 27 days agoApache-2.0View on GitHub

Create a new Remotion video

  • Reads credentials
  • Installs packages

31 other projects use a version of this, 31 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use remotion-license, mediabunny and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mia-cxSkill

    remotion-license

    Find Remotion license information, FAQs, terms, and where to buy a license.

    Also in 5 projects that use this

  • gabros20Skill

    mediabunny

    Multimedia handling with the Mediabunny library

    Also in 4 projects that use this

  • AnasX7Skill

    high-end-visual-design

    Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.

    Also in 3 projects that use this

  • AnasX7Skill

    minimalist-ui

    Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.

    Also in 3 projects that use this

  • delphi-aiSkill

    animate

    Animation patterns and best practices for Next.js/React applications. Use this skill when implementing animations, transitions, hover effects, page transitions, modals, or any motion in React components. Based on Emil Kowalski's "Animations on the Web" course.

    Also in 3 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 4 projects that use this

  • +1 more from AnasX7

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 5 are common, 1 is distinctive, and 7 are very specific to this project.

  • 5

    Common

    Most of the 31 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    If this is not the next task, see Remotion Best Practices

    line 9
  2. Very specific:

    If a project already exists, skip this.

    line 13
  3. Very specific:

    Ensure Node.js and Git is installed, and the current folder is appropriate for starting a new project.

    line 14
  4. Very specific:

    If it is empty, or contains only disposable operating-system metadata such as .DS_Store, create the project directly in the current folder.

    line 20
  5. Very specific:

    Remove only those disposable metadata files first, since create-video rejects non-empty folders.

    line 21
  6. Very specific:

    Do not treat all hidden files as disposable: files such as .env and directories such as .git are meaningful contents.

    line 22
  7. Very specific:

    If the current folder contains meaningful contents and no project already exists, scaffold into a new subfolder.

    line 33
  8. Common:

    Keep the scaffold and add React Markup.

    line 48
  9. Common:

    Follow Remotion React Markup Best Practices and Video Layout Rules for video-first layout and text sizing guidance.

    line 49
  10. Very specific:

    Before writing the root that registers <Composition> or <Still> elements, follow Compositions and stills.

    line 51
  11. Distinctive:

    If the video arranges multiple video or audio clips on a timeline, follow Video editing before writing the timeline.

    line 56
  12. Common:

    If this is a video with multiple subsequent scenes, follow guidance at Multi-scene videos.

    line 63
  13. Common:

    If Tailwind is requested, see tailwind.md for using TailwindCSS in Remotion.

    line 71

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

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.

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 for video-first layout and text sizing guidance.

Before writing the root that registers <Composition> or <Still> 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 for using TailwindCSS in Remotion.

Follow-up

The video creation process has finished. For follow-up prompts, use Remotion Best Practices

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.