motion-design
/motion-design
Projektuje animacje interfejsu zgodnie ze standardami systemu projektowego: czasy trwania, krzywe, przejścia i stany ładowania.
- Autor
- devpilotX ↗
- Repozytorium
- ai-skill-ai ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 31.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 31.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/motion_lint.py
Co robi i kiedy
Projektuje animacje interfejsu zgodnie ze standardami systemu projektowego: czasy trwania, krzywe, przejścia i stany ładowania.
Oryginalny opis (EN)
Design interface animation and transitions to design-system standards. Use when the user asks to animate a UI, add transitions, page or route transitions, scroll effects, micro-interactions, loading and skeleton states, hover and press feedback, or a motion token system; when a change adds keyframes, a scroll-driven effect or an animation library; or before shipping a page that moves. Sets duration and easing tokens from Material 3 and Carbon, caps stagger and distance, requires a prefers-reduced-motion branch and a pause control for anything that loops or runs past five seconds, and keeps ani
Jak działa
- When to use and when to stay off
- Non-negotiables
- Procedure
- Self-audit
- What this cannot do
Podgląd SKILL.md
---
name: motion-design
description: Design interface animation and transitions to design-system standards. Use when the user asks to animate a UI, add transitions, page or route transitions, scroll effects, micro-interactions, loading and skeleton states, hover and press feedback, or a motion token system; when a change adds keyframes, a scroll-driven effect or an animation library; or before shipping a page that moves. Sets duration and easing tokens from Material 3 and Carbon, caps stagger and distance, requires a prefers-reduced-motion branch and a pause control for anything that loops or runs past five seconds, and keeps animation on compositor-only properties. Verifies library licences and browser support live. Triggers on animate this, add a transition, page transition, scroll animation, micro-interaction, motion system, reduced motion, framer motion, gsap, lottie, rive. For the static visual layer (type, colour, spacing, tokens) use visual-design. For the 3D canvas use web-3d. For slow pages with no motion symptom use performance-tuning.
license: MIT
metadata:
version: 1.0.0
suite: ai-skill
---
# Motion design
Most interface animation is added after the layout is done, by reflex: a fade here, a slide there, a
card grid that springs in on scroll. The result moves a lot and means nothing, and it punishes anyone
on a slow device or with a vestibular disorder. This skill treats motion as a design material with a
budget. Every animation answers a question the user is already asking, runs on tokens shared across
the product, and has a path for people who asked their system for less movement.
## When to use and when to stay off
Run when the work adds or changes movement: entrance and exit transitions, page or route transitions,
scroll-linked effects, hover and press feedback, loading and skeleton states, list reordering, a
motion token set, or a choice between animation libraries. Also run before shipping a page that moves,
to check it against the budget below.
Stay off, and route instead, when:
- The work is the static visual layer: type scale, colour, spacing, radius, the token system itself. Use `visual-design`. Motion tokens extend that token set and should not contradict it.
- The work is a WebGL or Three.js canvas. Use `web-3d`; it owns scene budgets and its own frame-loop rules. Come back here only for the DOM chrome around the canvas.
- The page is slow and nothing is animating wrong. Use `performance-tuning` for the measurement, then return if the fix involves animation.
- The animation is a brand asset such as an animated logo. Use `brand-logo` for construction, this skill for how it plays in the interface.
- The work is a native mobile screen. Use `mobile-build`; platform motion systems differ.
The user says "stop", "I've decided", or "just execute": comply at once and stay off for the rest of
the session unless asked again.
## Non-negotiables
These override everything else in this file.
1. Every animation states its job before it is written: it shows a relationship (this came from there), confirms an action, directs attention, or covers latency. Decoration with no job is cut, not toned down.
2. A `prefers-reduced-motion: reduce` branch exists for any file that animates. Under it, movement that travels or scales is replaced by an opacity change or removed; it is not left running at a shorter duration. Essential motion that conveys information may stay, and is named as essential.
3. Anything that loops, autoplays, or runs longer than five seconds has a visible pause or stop control. This is WCAG 2.2.2, a Level A requirement, not a preference.
4. Animate compositor-only properties: `transform` and `opacity`, plus `filter` where the budget allows. Never animate `width`, `height`, `top`, `left`, `margin`, `padding` or anything else that forces layout, because it runs on the main thread and drops frames.
5. Durations and easings come from a shared token set, not per-component literals. Duration scales with the distance and size of the moving object; a token is picked, not invented at the call site.
6. Entrance animations play once per element per view. A card that re-animates every time it scrolls back into view is scroll-jacking by another name.
7. No scroll-jacking: the page never hijacks the native scroll speed or direction, never pins the user in place to force a sequence, and parallax stays subtle enough that reduced motion can switch it off with no loss of meaning.
8. Library licences and browser support are verified live before a recommendation, with a dated source. Free today is not free forever, and a feature that works in one engine is not a cross-browser plan.
## Procedure
Token values, easing curves, per-pattern durations and the reduced-motion recipes are in
`references/tokens-and-recipes.md`; read it before writing any animation.
### Step 1, name the job and pick the pattern
For each proposed animation, write one line: what the user is doing, what the motion tells them, and
what breaks if it is absent. If that line is hard to write, the animation has no job. Cut it and move
on.
Match the interaction to a known pattern rather than an invented one: container transform for a card
opening into a detail, shared-axis for forward and back in a flow, fade-through for an unrelated swap,
a skeleton or a spinner for latency past about 400ms, a 100ms press response for a tap. The patterns
and their reference systems (Material 3, IBM Carbon) are in the reference file.
### Step 2, set the token scale
Define duration and easing tokens once, keyed to the design system the product already uses. Material
3 groups durations as short, medium, long and extra-long and pairs them with standard and emphasised
easing; Carbon splits productive motion (short, functional) from expressive motion (longer, for larger
or brand moments). Pick one vocabulary and map every animation onto it.
Rule of thumb for duration, refined by the reference file: small elements and short distances 100 to
200ms; medium transitions 200 to 300ms; large or full-screen transitions 300 to 500ms; anything past
500ms needs a reason. Exits are usually faster than entrances.
### Step 3, build with reduced motion from the start
Write the reduced-motion branch in the same change as the animation, never as a follow-up. The default
shape:
```css
@media (prefers-reduced-motion: reduce) {
*, *::before, *::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
```
Use that as a floor, then override per component where a fade should remain. For motion driven in
JavaScript, read the same signal (`window.matchMedia('(prefers-reduced-motion: reduce)')`, or the
library's own hook such as Motion's `useReducedMotion`) and branch there too, because the CSS media
query does not reach a value tweened in script.
### Step 4, keep it on the compositor
Animate `transform` and `opacity`. Where a layout change is unavoidable, use the FLIP technique
(measure first, last, invert with a transform, play) so the visible animation is still a transform.
Use `will-change` only on the handful of elements about to animate, and remove it when the animation
ends; leaving it on many elements costs memory and can make things slower, not faster.
For scroll effects, prefer CSS scroll-driven animations (`animation-timeline: scroll()` or `view()`)
where support allows, with a static fallback for engines that lack it, over a JavaScript scroll
listener that runs work on every scroll event.
### Step 5, choose a library only if the platform cannot do it
CSS transitions and keyframes, the Web Animations API, and the View Transitions API cover most
interface motion with no dependency. Reach for a library when you need orchestration, spring physics,
layout animations, gesture-driven motion, or a designer-authored timeline. Match the tool to the need
and record the licence, verified live, from `references/tokens-and-recipes.md`:
- Declarative React motion, layout transitions, gestures: Motion (formerly Framer Motion), MIT.
- Complex timelines, scroll orchestration, SVG morphing, no framework: GSAP, now free under Webflow's "no charge" licence but not an open-source licence (see the reference file for the restriction).
- Designer-authored vector animation shipped as data: Lottie or dotLottie, MIT runtime.
- Interactive, state-machine-driven animation: Rive, open-source runtimes.
- One-line list and presence transitions: AutoAnimate, MIT.
### Step 6, lint and measure
Run the linter on every file that animates:
```
python3 scripts/motion_lint.py src/
```
It flags animation of layout properties, transitions longer than the threshold, infinite or long
animations with no pause control or reduced-motion branch, files that animate with no
`prefers-reduced-motion` anywhere, and `will-change` overuse. Fix high and medium findings before
shipping.
Then measure on a mid-range device, not a workstation: watch for dropped frames in the browser's
performance panel during the animation, and watch Interaction to Next Paint (INP), since motion that
blocks the main thread during a tap shows up there. A smooth animation on a fast laptop is not
evidence.
## Self-audit
- Every shipped animation has a one-line job; none is decoration with no job.
- Every file that animates has a `prefers-reduced-motion` branch, and JavaScript motion reads the same signal.
- Everything that loops, autoplays or runs past five seconds has a pause or stop control.
- No animation touches `width`, `height`, `top`, `left`, `margin` or `padding`; motion is on `transform` and `opacity`.
- Durations and easings come from tokens, scaled to distance and size; nothing runs past 500ms without a stated reason.
- Entrance animations play once per element per view; the page does not hijack scroll.
- Every recommended library has a licence and a browser-support note with a dated source.
- `scripts/motion_lint.py` runs clean at medium and above, or every remaining finding is explained.
- Motion was checked on a mid-range device, with the command or panel named.
## What this cannot do
It cannot measure frame rate or INP for you. The linter reads source; the performance claim needs a
real run on a real device, and this skill names what to run, not the result.
It cannot decide a licence's fit for your specific use. GSAP's current terms are free to use but are a
proprietary "no charge" grant from Webflow with prohibited uses and a termination clause, not an OSI
open-source licence; whether that risk is acceptable for a given project is a commercial and legal
judgement. For a product where the animation layer is load-bearing and the licence terms matter, ask a
technology or IP lawyer: "Does this component's licence permit our commercial use, redistribution and
modification, and what happens to us if the grantor revokes or changes it?"
It cannot confirm a feature works across browsers from documentation alone. Support tables move; test
the real target browsers, including the reduced-motion and no-JavaScript paths, before calling it done.
Pliki w paczce (3)
- SKILL.md 11 KB
- references/tokens-and-recipes.md 10 KB
- scripts/motion_lint.py 14 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · devpilotX/ai-skill-ai | 100 | MIT |
| quangphung218/contour-design | 100 | Apache-2.0 |
| nexu-io/open-design | 100 | Apache-2.0 |
| cdeweyx/conor-os | 100 | MIT |
| nextwork-projects/ai-video-editor-cooked | 100 | MIT |
| jairotorregrosa/jaiskills | 100 | MIT |
| 1AngelMicka/ultimate-motion-design | 100 | MIT |
| nguyenthienthanh/aura-frog | 100 | MIT |
| sapraudnynew/explain-ladder | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki c33df963860c (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90css-animation-creator
Tworzy animacje CSS, przejścia, mikrointerakcje i złożony motion design: efekty hover, stany ładowania, przejścia stron i animacje przewijania. - 100animation-motion-design
Wdraża animacje komponentów i przejścia stron w Motion oraz View Transitions API, z obsługą ograniczonego ruchu i gestów. - 100interaction-motion-design
Projektuje mikrointerakcje i animacje: czasy i krzywe easing, fizykę sprężyn, choreografię przejść, słownik haptyczny i emocjonalny design, z obsługą prefers-reduced-motion. - 100animation-motion-design
Podaje wzorce animacji i projektowania ruchu z biblioteką Motion i View Transitions API, w tym przejścia stron i prefers-reduced-motion. - 90fe-motion
Dodaje płynne, bezpieczne animacje na transform i opacity, z obsługą prefers-reduced-motion, pauzą dla treści odtwarzanych automatycznie i sprawdzaniem funkcji. - 100vyson-css-motion
Dodaje do strony dostępne animacje samym CSS, np. wejścia, reveal przy scrollu i przejścia, z obsługą redukcji ruchu.