film-component
Skill207 starsChanged 34 days agoMITView on GitHub
Render a video of an audio/ui component with the Remotion app in apps/video (a new component, an updated one, the whole library, or the teaser), or add or fix a component's showcase. Use when the user asks for a video, a clip, a render or a teaser of a component.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/audio-ui/AGENTS.mdAGENTS.md
- skills/core/AGENTS.mdAGENTS.md
- skills/design/AGENTS.mdAGENTS.md
- skills/web-audio/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- add-registry-itemSkill
- change-primitiveSkill
- audio-uiSkill
- coreSkill
- designSkill
- web-audioSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 20
Add --theme dark for the dark theme.
- Very specific: line 26
Check it in bun run studio before rendering.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Film a component
The full guide is apps/video/README.md: read it first. Commands run from apps/video/; videos land in out/ (1920×1080, 60 fps, landscape only).
bun run new <name> # first release, "New component" badge
bun run update <name> --note "…" --note "…" # up to 3 notes; without --note they come from pending changesets
bun run showcase <name> # no status
bun run all # every component
bun run teaser # the 28 s library teaser
bun run stars # a thank you for the GitHub stars (reads the count with gh)
bun run studio # preview, under ShowcasesAdd --theme dark for the dark theme.
A component without a showcase
src/showcases/<name>.tsx: a component taking{ t }(seconds on screen) that renders the real registry element from@/registry-audio/.... Every value is computed fromt: no state, no effects that animate. A frame is a pure function oft.- List it in
src/showcases/index.tswith its title and its size alone on screen. - Check it in
bun run studiobefore rendering.
Gotchas
- Remotion seeks frames, it doesn't play them: CSS transitions and animations are off (
src/styles.css). Anything that moves must come fromt. IconPlaceholderis stubbed bysrc/icon-placeholder.tsx(the real one pulls in the whole design system) and draws only the Lucide icons in itsICONSmap. Any other icon renders nothing: add it there.webpack-override.tsforces the automatic JSX runtime and resolves@/and@audio-ui/*to their sources. Restart the studio after changing it orremotion.config.ts. The config compiles to CommonJS, so noimport.meta.- One continuous camera, one object morphing into the next: no cuts, no crossfades, no overshoot.
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
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.

