ui-component-clip
Skill18 starsChanged 47 days agoMITView on GitHub
Make a short, seamless video loop of one real interface component or interaction. Use for buttons, toggles, overlays, waveforms, loading states, and small product details.
In this repository10 other files it gives its agents.
- brand-filmSkill
- brand-grid-videoSkill
- creator-videoSkill
- feature-videoSkill
- narrated-product-filmSkill
- silent-product-demoSkill
- social-video-hooksSkill
- ui-tutorial-videoSkill
- video-brand-systemSkill
- video-thumbnailsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Keep the pointer only if it explains how the state changes.
- Distinctive: line 21
Leave enough time at the settled state to understand the result.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
UI component clip
Make one component the subject. A useful clip is usually three to six seconds with one action, a clear state change, and a clean loop. It should work in a reply or product page without a title or outro.
Ground the design
Inspect the real component and its styles before animating it. Use its actual dimensions, text, color, border, shadow, states, and entrance timing. Capture the running UI when possible. If rendering the component in a video composition, port the relevant source faithfully and keep animation driven by the video frame, not browser time.
Choose a quiet background from the product's visual system. Keep the camera locked or make one subtle push; the interaction is the event. Add a label only when the component cannot explain itself.
Build the loop
- For periodic motion, fit whole cycles inside the duration so the last state meets the first.
- For a one-time action, show the result briefly, then return to the starting state through a plausible reverse action or an edit on a still frame.
- Keep the pointer only if it explains how the state changes. Its tip should land on the actual hit target and remain there through the click.
- Leave enough time at the settled state to understand the result.
Compare the first and last frames and watch several repeats. A single-frame jump, double trigger, or moving object appearing in two places breaks the loop. Export the requested ratios and check that the component remains legible in each one.
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.

