Skip to content
Back to skills

Ui Component Clip

ASecurity

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.

  • 214 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 1, 2026
design

Works with

  • cli

Security analysis

A100/100

Pro scans all 13 files and shows the line behind each finding

Scanned October 1, 2026

npx -y skills add NeverSight/skills_feed --skill ui-component-clip --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ui Component Clip?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ui Component Clip
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/neversight-ui-component-clip/badge)](https://www.skillsdirectory.com/skills/neversight-ui-component-clip)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ui-component-clip
description: 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.
---

# 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.

Files in this skill

  • SKILL.md1.7 KB
  • description_ar.txt330 B
  • description_cn.txt151 B
  • description_de.txt218 B
  • description_en.txt172 B
  • description_es.txt220 B
  • description_fr.txt248 B
  • description_it.txt222 B
  • description_ja.txt290 B
  • description_ko.txt229 B
  • description_ru.txt389 B
  • description_tw.txt160 B
  • stats.json68 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…