motion
Skill4 starsChanged 13 days agoMITView on GitHub
Web animation + short-video knowledge for design-builder. Two modes: (1) UI motion in production web apps — GSAP / WAAPI / CSS / Anime.js / Lottie / Three.js library patterns, easing, stagger, performance, prefers-reduced-motion, motion anti-slop; (2) short video generation via HyperFrames (HTML compositions, CLI, scene transitions, captions). Activated by /build, /improve, /design_page, /design_screen when motion is part of the spec — and standalone when the user asks for animation help or a video. Sister skill to `design`; lives under skills/motion/.
38 other projects use a version of this.
Adopted by
Most recently taken up by
- sanmidable/skillstheir own version, first seen Nov 8, 2026
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- RuneStone-Tech/optimize-anythingtheir own version, first seen Nov 8, 2026
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 3, 2026
- seanx10m/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use defaults, viewports and 9 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.
sanmidableSkilldefaults
Also in 3 projects that use this
sanmidableSkillviewports
Also in 3 projects that use this
miovragSkillkeyboard
Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.
Also in 3 projects that use this
soilmassSkillcolor
Color animations including hue shifts, saturation changes, brightness transitions, and contrast adjustments. Use when implementing color morphing, theme transitions, mood effects, or attention-grabbing color pulses. Provides tokens for all color property animations.
Also in 4 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 3 projects that use this
GoogleSkillcritique
Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.
Also in 4 projects that use this
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- theexperiencecompany/gaia★ 325same name
- Mindrally/skills★ 275same name
- raphaelsalaja/skills★ 62same name
- podo/design-agent-skills★ 32same name
- muzimu217/ui-design-agent-kit★ 23same name
- imMamdouhaboammar/linkedin-animated-infographics★ 14same name
- icons8/agent-skills★ 12same name
- lalulali/vespyr★ 11same name
- sukirman1901/frontend-expert★ 9same name
- Felipeex/motion-skill★ 3same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- design-builderSkill
- designSkill
- figma-useSkill
- playwright-cliSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If motion is not part of the request, do nothing.
- Distinctive: line 36
If the request is ambiguous ("can you make the landing more dynamic?"), default to web-ui mode.
- Very specific: line 79
When /improve or /review runs, route motion concerns through references/anti-patterns.md.
- Very specific: line 97
When the user asks for a video, this skill is the primary skill (not design).
“Common” is measured: kept by at least 6 in 10 of the 32 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.
Files
HyperFrames CLI requires Node >=22 in verified version 0.8.225 (2026-11-01); check installed engines and CLI help before video workflows.
Motion Knowledge Base — for design-builder
You are the motion knowledge layer of design-builder. The sister design skill owns the three-layer architecture (Layer 1 facts → Layer 2 filters → emit). This skill plugs into both:
- Layer 1 (
KB-EXTENSION) — library-level animation knowledge that theanimationsMCP type alone does not cover (easing curves, registration patterns, performance, accessibility). - Layer 2 (Anti-Patterns) — motion-specific anti-slop rules listed in
references/anti-patterns.md.
You activate when:
- A spec generated by
/design_pageor/design_screenlists motion in itsanimation:block, and/buildis now emitting code. /improveis asked to add or fix motion on user code.- The user explicitly asks for animation help on their web app.
- The user asks for a short video — switch to video mode (HyperFrames pipeline).
If motion is not part of the request, do nothing. Don't volunteer animation suggestions from this skill unless the spec calls for them — gratuitous motion is the #1 way design-builder produces AI slop.
Mode router (read first)
| Signal | Mode | Primary refs |
| Production web app, React/Next/Svelte/etc., motion is incidental to the UI | web-ui | references/selection.md → pick library → corresponding references/web-animations/*.md |
| User asked for a short video, intro/outro, social ad, product promo, hero loop rendered to MP4/WebM | video | references/video/hyperframes.md + references/video/hyperframes-cli.md |
| Lottie file already exists or the user mentions After Effects / Bodymovin export | either mode | references/web-animations/lottie.md |
| 3D / WebGL hero, product spin, shader plate | web-ui (if interactive) or video (if pre-rendered) | references/web-animations/three.md |
If the request is ambiguous ("can you make the landing more dynamic?"), default to web-ui mode. Switch only when the user explicitly says "render", "video", "MP4", or names a length in seconds with a delivery target (Instagram, Twitter, YouTube short).
Web-UI mode — the contract
You are writing motion that ships in a real web app. That means:
- Honor
prefers-reduced-motion: reduce— every motion path must collapse to a non-motion variant. For GSAP usegsap.matchMedia(); for CSS use@media (prefers-reduced-motion: reduce); for WAAPI gateelement.animate()behind a JS check. - Stay on the compositor — animate
transformandopacityonly.width,height,top,left,margincause layout thrash. The library refs all repeat this rule; enforce it. - Finite duration, finite repeats — even for "ambient" loops, prefer a finite repeat count tuned to a known cycle length, with a clean exit. Infinite animations break tab-switch heuristics, drain battery on mobile, and hide animation bugs.
- No render-blocking JS — initialize animations after the relevant DOM exists, but don't gate first paint on an animation library load. Lazy-import GSAP/Anime.js for non-above-the-fold motion.
- Pick one library per concern — don't mix GSAP and Anime.js in the same file. Don't drive a CSS keyframe with WAAPI's
animate(). The selection table inreferences/selection.mdis the decision tree.
Video mode — the contract
You are emitting an HTML composition that HyperFrames will seek and screenshot frame-by-frame, then encode to MP4/WebM with FFmpeg. That means:
- Deterministic — no
Math.random(),Date.now(),performance.now(),requestAnimationFrameas source of truth. Use seeded PRNGs (mulberry32) when randomness is needed. - Synchronous setup — build timelines and register them on
window.__timelines[<composition-id>]synchronously after page load. Noasync, nosetTimeout, no Promises. - Finite everything — no
repeat: -1, no infinite CSSanimation-iteration-count. Compute repeats from the composition duration. - Library adapters — HyperFrames seeks GSAP via
window.__timelines, Anime.js viawindow.__hfAnime, Lottie viawindow.__hfLottie, Three.js via thehf-seekevent. Each library ref documents its registration contract. - CLI workflow — every video composition ends with
npx hyperframes lint && npx hyperframes inspect && npx hyperframes render. Skip lint and you'll ship broken frames. Seereferences/video/hyperframes-cli.md.
Library quick-reference (decision matrix)
Full guidance: references/selection.md. One-line summary:
| Library | When to reach for it | Web-UI ref | Video ref |
| CSS animations | Decoration, shimmer, glow, single-element entrances. No JS dependency. | web-animations/css.md | same |
| WAAPI | Native browser keyframes, no library, JS-driven timing without GSAP weight. | web-animations/waapi.md | same |
| GSAP | Scene choreography, complex stagger, timeline sequencing, scroll-driven motion. The default for non-trivial UI motion. | web-animations/gsap.md | required for video mode |
| Anime.js | Compact SVG/DOM flourishes when the user already uses it; otherwise prefer GSAP. | web-animations/anime.md | same |
| Lottie | After Effects exports, logo reveals, illustrative micro-anims authored by a designer. | web-animations/lottie.md | same |
| Three.js | 3D, WebGL, shader plates, particles. Heavy — justify the bundle cost. | web-animations/three.md | same |
Anti-patterns (Layer 2 hook)
When /improve or /review runs, route motion concerns through references/anti-patterns.md. The list includes:
- Linear easing on UI motion (always reads as "AI default" — use
power2.out/cubic-bezier(0.2, 0, 0, 1)etc.) - Motion without a
prefers-reduced-motionfallback - Animating layout properties when transforms work
- Infinite loops without a defined cycle exit
- Parallax/scroll-driven motion that ignores reduced-motion or mobile
- Multiple competing animation libraries in the same component
- Entrance animations on every element on first paint (delay above-the-fold motion to after LCP)
- Decorative motion that interferes with reading (auto-rotating carousels < 8s, infinite text marquees)
Integration with /build, /improve, /design_page, /design_screen
/design_pageand/design_screenmay include ananimation:block in the spec. If they do, this skill is the source for what library to recommend and the patterns the spec should reference./buildreads the spec and, when theanimation:block exists, consults this skill to emit production-ready library code. The skill does not emit code itself —/builddoes, this skill informs./improveconsults thereferences/anti-patterns.mdchecklist when motion is in scope of the improvement target.- When the user asks for a video, this skill is the primary skill (not
design). The video pipeline is self-contained underreferences/video/.
References (loaded on demand)
Web-UI mode
references/selection.md— pick the right library for a given motion job. Decision tree.references/web-animations/css.md— CSS keyframes,animation-fill-mode,prefers-reduced-motion.references/web-animations/waapi.md—element.animate(), KeyframeEffect, currentTime seeking.references/web-animations/gsap.md— tweens, timelines, easing, stagger,matchMedia, performance.references/web-animations/anime.md— Anime.js v4 patterns.references/web-animations/lottie.md—lottie-weband dotLottie players.references/web-animations/three.md— Three.js scenes, GLTF + AnimationMixer.
Video mode
references/video/hyperframes.md— composition authoring contract: data-attributes, timeline registration, scene transitions, layout-before-animation rule.references/video/hyperframes-cli.md—npx hyperframes init / lint / inspect / preview / render / transcribe / tts.references/video/tailwind-runtime.md— Tailwind v4 browser runtime wheninit --tailwindis used.
Cross-cutting
references/anti-patterns.md— motion anti-slop rules. Consumed by/improveand/review.
Source attribution
The library and HyperFrames knowledge in references/ is adapted from the open-source heygen-com/hyperframes skill set (vendored at .agents/skills/, lockfile skills-lock.json). Original skills are HyperFrames-contract-first; the references in this folder strip the seek/contract sections for web-UI mode and keep them for video mode. License attribution lives in NOTICE.md.
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.

