Frontend Motion and Interaction
Motion should clarify structure, provide feedback, or create one memorable moment.
Avoid scattered animation that competes with the interface.
Motion Strategy
- Choose the role: orientation, feedback, delight, continuity, or emphasis.
- Define one primary moment: page load, hero interaction, panel transition, or data reveal.
- Keep secondary motion quiet.
- Respect reduced-motion preferences.
Patterns
- Page load: staggered entrance with short delays and consistent easing.
- Hover: small transform, color, elevation, or reveal tied to affordance.
- Press: immediate tactile feedback.
- Layout transition: preserve spatial continuity.
- Data reveal: animate changes only when it improves comprehension.
- Scroll effects: use sparingly and avoid blocking content access.
Timing
- Micro-interactions: 120-220ms.
- UI transitions: 180-350ms.
- Large hero moments: 400-800ms when appropriate.
- Use one easing family per interface.
Implementation
- Prefer CSS transitions for simple effects.
- Use Framer Motion when coordinating React state, route transitions, or complex sequencing.
- For React projects, public libraries such as React Bits can be useful references for text effects, animated backgrounds, and interactive components. Treat them as optional dependencies: verify license, bundle impact, accessibility, reduced-motion behavior, and project fit before adding.
- Avoid animation that changes layout unexpectedly.
- Provide
prefers-reduced-motion fallbacks.
Ownership
- Own motion intent: orientation, continuity, feedback, hierarchy, and deliberate
delight.
- Separate design motion from runtime latency, data loading, and jank. Runtime
performance defects go back to implementation/testing; do not invent a
universal cross-project millisecond budget as a design rule.
- Motion should support F-C actual-surface convergence: verify that animation
does not hide content, break focus, misrepresent state, or create a competing
interaction path.
Verification
Confirm animations do not cause jank, obscure text, trap focus, or delay primary tasks.
1---2name: motion-interaction3description: "Design and implement frontend motion: page-load choreography, transitions, hover states, scroll effects, feedback animation, and reduced-motion behavior. Use when adding or reviewing animation and interaction polish."4status: active5provenance: local6trusted: false7requires_network: false8writes_files: true9executes_code: false10secrets_needed:11last_reviewed: 2026-07-1312profile_tags:13recommended_scope: project14icon_small: assets/app-facing.svg15icon_large: assets/app-facing.svg16metadata:17 source: https://skillmd.com/skills/yuukias/motion-interaction18---1920# Frontend Motion and Interaction2122Motion should clarify structure, provide feedback, or create one memorable moment.23Avoid scattered animation that competes with the interface.2425## Motion Strategy26271. Choose the role: orientation, feedback, delight, continuity, or emphasis.282. Define one primary moment: page load, hero interaction, panel transition, or data reveal.293. Keep secondary motion quiet.304. Respect reduced-motion preferences.3132## Patterns3334- Page load: staggered entrance with short delays and consistent easing.35- Hover: small transform, color, elevation, or reveal tied to affordance.36- Press: immediate tactile feedback.37- Layout transition: preserve spatial continuity.38- Data reveal: animate changes only when it improves comprehension.39- Scroll effects: use sparingly and avoid blocking content access.4041## Timing4243- Micro-interactions: 120-220ms.44- UI transitions: 180-350ms.45- Large hero moments: 400-800ms when appropriate.46- Use one easing family per interface.4748## Implementation4950- Prefer CSS transitions for simple effects.51- Use Framer Motion when coordinating React state, route transitions, or complex sequencing.52- For React projects, public libraries such as React Bits can be useful references for text effects, animated backgrounds, and interactive components. Treat them as optional dependencies: verify license, bundle impact, accessibility, reduced-motion behavior, and project fit before adding.53- Avoid animation that changes layout unexpectedly.54- Provide `prefers-reduced-motion` fallbacks.5556## Ownership5758- Own motion intent: orientation, continuity, feedback, hierarchy, and deliberate59 delight.60- Separate design motion from runtime latency, data loading, and jank. Runtime61 performance defects go back to implementation/testing; do not invent a62 universal cross-project millisecond budget as a design rule.63- Motion should support F-C actual-surface convergence: verify that animation64 does not hide content, break focus, misrepresent state, or create a competing65 interaction path.6667## Verification6869Confirm animations do not cause jank, obscure text, trap focus, or delay primary tasks.