← ClaudeAtlas

motion-meaninglisted

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.
SoraLabsOSS/skills · ★ 29 · Web & Frontend · score 73
Install: claude install-skill SoraLabsOSS/skills
# 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](references/CLASSIFY.md) | | Reduce strategies + picture stories | [references/STRATEGIES.md](references/STRATEGIES.md) | | Audit / fix existing code | [references/AUDIT.md](references/AUDIT.md) | | Code patterns (CSS / JS / React) | [references/PATTERNS.md](references/PATTERNS.md) | | Failure modes | [references/FAILURES.md](references/FAILURES.md) | | Done coding | [references/VE