agentleFS
Sign inStart free
mumudevxmumudevx/agent-skills/remotion/SKILL.md

remotion-best-practices

Skill0 starsChanged 9 months agoNo licenceView on GitHub

Best practices for Remotion - Video creation in React

149 other projects use a version of this, 104 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ltx2, canvas-procedural-animation and 10 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.
  • LinHao-citySkill

    ltx2

    AI video generation with LTX-2.3 22B — text-to-video, image-to-video clips for video production. Use when generating video clips, animating images, creating b-roll, animated backgrounds, or motion content. Triggers include video generation, animate image, b-roll, motion, video clip, text-to-video, image-to-video.

    Also in 6 projects that use this

  • LinHao-citySkill

    canvas-procedural-animation

    Use p5.js/canvas for local procedural character effects: particles, weather, squash/stretch, walk cycles, and environmental motion.

    Also in 5 projects that use this

  • OpenAISkill

    remotion-saas

    Build an app with Remotion

    Also in 21 projects that use this

  • OpenAISkill

    remotion-maps

    Remotion Map animation knowledge

    Also in 17 projects that use this

  • mia-cxSkill

    remotion-license

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

    Also in 4 projects that use this

  • +5 more from openai
  • +2 more from LinHao-city

The file

We split this skill into the rules it gives an agent

7 rules. 1 is common, 6 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 146 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 146 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.

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.

Check your setup, free