lottiefiles-motion-design-skill

Guides UI animation decisions using timing, easing, choreography, and Disney motion principles.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/design-skills --skill lottiefiles-motion-design-skill-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lottiefiles-motion-design-skill
Source: https://github.com/reason-machines/design-skills/tree/main/skills/lottiefiles-motion-design-skill
Command: npx skills add https://github.com/reason-machines/design-skills --skill lottiefiles-motion-design-skill-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI animations often feel robotic, janky, or inconsistent because developers write animation code without a motion design framework. This Skill provides a philosophy-first decision process (WHY → WHAT → HOW) so animations have clear purpose, appropriate timing, and brand-consistent personality before any code is written. ## Core Features & Use Cases - Motion Decision Framework: An 8-step checklist covering purpose, emotion, personality, properties, duration, easing, choreography, and quality for every animation. - Ready-to-Use Patterns: Implementation recipes for button states, card entrances, loading/success/error transitions, staggered lists, and modal enter/exit in CSS, Framer Motion, GSAP, Svelte, and Angular. - Reference Tables: Duration-by-element-size and easing-by-intent lookup tables, plus Disney's 12 principles adapted for UI. - Use Case: When building a submit button that transitions from idle to loading to success, use this Skill to select a 200ms easeOut scale transition, a success bounce with easeOutBack, and an error shake, then verify it against the quality checklist. ## Quick Start Ask the agent to add a natural-feeling entrance animation to a card component and review it against the motion design checklist.

Frequently Asked Questions about lottiefiles-motion-design-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right easing curve for a UI animation?▼

Match easing to intent: use easeOut (0, 0, 0.2, 1) for elements entering, easeIn (0.4, 0, 1, 1) for exits, easeInOut for position changes, and easeOutBack for attention-grabbing success feedback. Never use linear easing, which feels robotic.

What duration should UI animations use?▼

Duration scales with element size: 150-200ms for icons and badges, 200-300ms for buttons and inputs, 300-400ms for cards, 400-500ms for modals and drawers, and 500-700ms for full page transitions.

Does this motion design approach work with Framer Motion and GSAP?▼

Yes, the principles are implementation-agnostic and include code examples for CSS transitions, Framer Motion variants, GSAP with Vue, Svelte transitions, and Angular animations. The timing and easing guidance transfers across all animation libraries.

Why does my animation stutter or feel janky?▼

Jank usually comes from animating layout properties like width, height, top, or left, which force reflows. Animate only transform and opacity, which are GPU-accelerated, and use will-change sparingly only during the animation.

How do I handle animations for users who prefer reduced motion?▼

Detect the prefers-reduced-motion media query and replace movement with simple opacity fades. In CSS, set animation and transition durations to near-zero inside a prefers-reduced-motion media block.

How do I choreograph multiple elements animating together?▼

Follow hierarchy, stagger, and overlap rules: animate the most important element first, stagger siblings by 50-150ms depending on desired drama, and group related elements so they move together following natural reading order.