agentleFS
ridelink0ridelink0/ultimate-frontend-skills/skills/remotion-video/SKILL.md

remotion-video

Skill7 starsChanged 13 days agoMITView on GitHub

Create and verify code-authored videos with Remotion, using the official Remotion skills as an explicit optional integration. Covers deterministic frames, composition registration, audio, rendering and runtime licensing.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use hyperframes-video.

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.
  • ieteerapatSkill

    hyperframes-video

    Create deterministic MP4 videos from HTML/CSS and seekable animations using the HyperFrames framework. Self-contained — no plugin required. Use whenever the user wants to generate a video, animation, product intro, social clip, data viz, chart race, captions, lower-thirds, or docs-to-video / PDF-to-video / website-to-video, or mentions hyperframes, GSAP timelines, or composition rendering.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the project's existing Remotion version and installed official remotion-best-practices, remotion-markup and remotion-render skills.

    line 8
  2. Distinctive:

    Create a registered composition.

    line 17
  3. Very specific:

    Use existing UFS references/motion-graphics.md and sound-design.

    line 19
  4. Distinctive:

    Test missing media, long text, changed input props, repeat renders and export failure.

    line 25

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

Remotion video creation

Use the project's existing Remotion version and installed official remotion-best-practices, remotion-markup and remotion-render skills. UFS registers remotion-dev/skills as an explicit source install; it never downloads Remotion during plugin install. Its skills snapshot has no root license file, so no upstream files are vendored. Review the runtime license for this user and use before installing or rendering. Do not label Remotion universally free.

  1. Define audience, message, source facts, dimensions, FPS, duration and export.
  2. Create a registered composition. Derive animation from frame/fps rather than wall-clock timers or Math.random; seed any intentional randomness.
  3. Use existing UFS references/motion-graphics.md and sound-design. Keep narration/caption timing explicit, media licensed, fonts local or loaded before rendering, and meaningful static/transcript alternatives.
  4. Render a still at start, transition boundaries and final hold. Inspect them. Render the actual output and verify duration, dimensions, decoder playback, clipping and audio sync. A successful install or typecheck is not a video.
  5. Test missing media, long text, changed input props, repeat renders and export failure. Do not claim a render ran unless its output exists and was checked.

The original UFS video CLI remains available for existing scene files; this skill adds a distinct Remotion route, not a silent runtime substitution.

An original, rendered reference ships in assets/example/README.md. Copy the example outside the plugin before installing its optional dependencies.

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.