Motion meaning
Web (CSS/JS/React + GSAP/Motion): classify UI motion as communicative (sequence is the content) or decorative (decorating a result), then fix or apply prefers-reduced-motion so meaning survives under reduce. Use when auditing existing animation, gating new motion, verifying both preference states, catching a dead reduced-motion branch, snapping to an end state, or collapsing a transition without nuking essential cues. Not for React Native, full WCAG encyclopedias, keyboard traps, color contrast, focus management, or ARIA pattern audits.From its SKILL.md
npx -y skills add SoraLabsOSS/skills --skill motion-meaningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
7.1 KB, as published. Nobody here has run it
Motion Meaning
Reduced motion isn't about removing animation. It's about deciding what remains when animation disappears.
Ask once, before writing or patching any reduce branch:
Is the motion sequence the content, or is it decorating a result that exists either way?
- Communicative (sequence = content) → keep the destination; change how you get there (snap end state, or reduce complexity).
- Decorative (decorating a result) → bail, or collapse the transition. No substitute required.
Grep for prefers-reduced-motion proves almost nothing. Touches ≠ reachable ≠ correct.
Read next
| Situation | Open |
|---|---|
| Pick a strategy | references/CLASSIFY.md |
| Reduce strategies + picture stories | references/STRATEGIES.md |
| Audit / fix existing code | references/AUDIT.md |
| Code patterns (CSS / JS / React) | references/PATTERNS.md |
| Failure modes | references/FAILURES.md |
| Done coding | references/VERIFY.md + scripts/verify-reduced.mjs |
| Sources & credit | references/CREDITS.md |
Four reduce strategies
Pick one of these for what the screen becomes under reduce. Picture the outcome first; then open STRATEGIES.md for the full story.
| # | Strategy | When | Under reduce looks like |
|---|---|---|---|
| 1 | Bail | Pure decoration; no honest reduced form | Effect is gone — OS cursor back, no custom layer |
| 2 | Snap to end state | Sequence is the content (staged journey) | Same final layout as the last frame of the full animation — no travel, no mid poses piled on screen |
| 3 | Collapse transition | Motion only decorates a result already in the DOM | Control jumps to the right place (tab pill, underline) — instant, not a slide |
| 4 | Reduce complexity | Cost/layers/autoplay matter, not only duration | Same silhouette, cheaper — fewer blur layers, autoplay off, fewer clones |
Always also — live preference (not a fifth “look”): read prefers-reduced-motion with a change listener (or library equivalent). One-shot .matches at mount goes stale mid-session. See PATTERNS.md.
Quick fork: decorative → 1 or 3. Communicative journey → 2. Still useful but heavy → 4.
The four gates
Every animation under authorship or audit passes all four. Verify by running both preference states — never by grepping alone. Details in VERIFY.md.
- Role — Communicative or decorative? (sequence = content?)
- Hazard — Large viewport motion, parallax, spin, autoplay >5s, seizure flash?
- Reduce path — Which strategy (1–4)? Is preference live?
- Meaning — With reduce on, can the user still know the state / outcome?
Author new motion
- Name the role (gate 1) out loud before keyframes.
- Pick strategy 1–4 from CLASSIFY.md — use the “looks like” column above.
- Wire a live preference read — PATTERNS.md.
- Implement the reduce branch inside the setup that also owns the full-motion path (avoid outer gates that skip the end-state applicator — FAILURES.md #1).
- Verify both states (VERIFY.md).
Companion: icon hover gestures from animating-icons are decorative → animation: none at rest. Icon-swap is communicative → instant coordinates, no tween.
Audit existing motion
- Inventory motion sources (CSS transitions/keyframes, WAAPI, GSAP, Motion, canvas, smooth-scroll hijack).
- Per item: run the four gates; assign a strategy.
- Report each finding as:
file:line+ quoted snippet- role + failure (one short sentence)
- concrete minimal fix
- Prefer targeted patches. Do not rewrite unrelated UI.
- Re-verify both preference states after the patch.
Full procedure: AUDIT.md.
Done checklist
- Role named (communicative vs decorative)
- Strategy 1–4 chosen; you can picture what “looks like” under reduce
- Preference is live (
changelistener — not one-shot at mount) - Reduce branch is reachable (not dead behind an outer
if (reduced) return) - Gate 4: meaning survives under reduce (end state / bail / collapse as intended)
- No
duration: 0on sequence-as-content without a snap end state - If something waits on
transitionend/onComplete, use~0.01msnot0s -
scripts/verify-reduced.mjs(or equivalent dual-state check) run on fixtures or the page - Autoplay >5s still has a pause control (WCAG 2.2.2) even when motion is allowed
- Interaction-triggered motion is disable-able via PRM unless essential (WCAG 2.3.3) — meaning still survives under the chosen strategy
Red flags — stop and re-derive
- "Just set
duration: 0everywhere" - Grep is green so shipping
- Outer
if (prefersReducedMotion) returnbefore the function that applies the end state - One-shot
matchMedia(...).matcheswith nochangelistener - Reduced path teleports overlapping mid-states instead of a single destination
- Decorative flourish kept "because it is small"