Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.
MANDATORY PREPARATION
Invoke /impeccable — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first. Additionally gather: performance constraints.
Assess Animation Opportunities
Analyze where motion would improve the experience:
Identify static areas:
- Missing feedback: Actions without visual acknowledgment (button clicks, form submission, etc.)
- Jarring transitions: Instant state changes that feel abrupt (show/hide, page loads, route changes)
- Unclear relationships: Spatial or hierarchical relationships that aren't obvious
- Lack of delight: Functional but joyless interactions
- Missed guidance: Opportunities to direct attention or explain behavior
Understand the context:
- What's the personality? (Playful vs serious, energetic vs calm)
- What's the performance budget? (Mobile-first? Complex page?)
- Who's the audience? (Motion-sensitive users? Power users who want speed?)
- What matters most? (One hero animation vs many micro-interactions?)
If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
CRITICAL: Respect prefers-reduced-motion. Always provide non-animated alternatives for users who need them.
Plan Animation Strategy
Create a purposeful animation plan:
- Hero moment: What's the ONE signature animation? (Page load? Hero section? Key interaction?)
- Feedback layer: Which interactions need acknowledgment?
- Transition layer: Which state changes need smoothing?
- Delight layer: Where can we surprise and delight?
IMPORTANT: One well-orchestrated experience beats scattered animations everywhere. Focus on high-impact moments.
Implement Animations
Add motion systematically across these categories:
Entrance Animations
- Page load choreography: Stagger element reveals (100-150ms delays), fade + slide combinations
- Hero section: Dramatic entrance for primary content (scale, parallax, or creative effects)
- Content reveals: Scroll-triggered animations using intersection observer
- Modal/drawer entry: Smooth slide + fade, backdrop fade, focus management
Micro-interactions
- Button feedback:
- Hover: Subtle scale (1.02-1.05), color shift, shadow increase
- Click: Quick scale down then up (0.95 → 1), ripple effect
- Loading: Spinner or pulse state
- Form interactions:
- Input focus: Border color transition, slight scale or glow
- Validation: Shake on error, check mark on success, smooth color transitions
- Toggle switches: Smooth slide + color transition (200-300ms)
- Checkboxes/radio: Check mark animation, ripple effect
- Like/favorite: Scale + rotation, particle effects, color transition
State Transitions
- Show/hide: Fade + slide (not instant), appropriate timing (200-300ms)
- Expand/collapse: Height transition with overflow handling, icon rotation
- Loading states: Skeleton screen fades, spinner animations, progress bars
- Success/error: Color transitions, icon animations, gentle scale pulse
- Enable/disable: Opacity transitions, cursor changes
Navigation & Flow
- Page transitions: Crossfade between routes, shared element transitions
- Tab switching: Slide indicator, content fade/slide
- Carousel/slider: Smooth transforms, snap points, momentum
- Scroll effects: Parallax layers, sticky headers with state changes, scroll progress indicators
Feedback & Guidance
- Hover hints: Tooltip fade-ins, cursor changes, element highlights
- Drag & drop: Lift effect (shadow + scale), drop zone highlights, smooth repositioning
- Copy/paste: Brief highlight flash on paste, "copied" confirmation
- Focus flow: Highlight path through form or workflow
Delight Moments
- Empty states: Subtle floating animations on illustrations
- Completed actions: Confetti, check mark flourish, success celebrations
- Easter eggs: Hidden interactions for discovery
- Contextual animation: Weather effects, time-of-day themes, seasonal touches
Technical Implementation
Use appropriate techniques for each animation:
Timing & Easing
Durations by purpose:
- 100-150ms: Instant feedback (button press, toggle)
- 200-300ms: State changes (hover, menu open)
- 300-500ms: Layout changes (accordion, modal)
- 500-800ms: Entrance animations (page load)
Easing curves (use these, not CSS defaults):
/* Recommended - natural deceleration */
--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1); /* Smooth, refined */
--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1); /* Slightly snappier */
--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1); /* Confident, decisive */
/* AVOID - feel dated and tacky */
/* bounce: cubic-bezier(0.34, 1.56, 0.64, 1); */
/* elastic: cubic-bezier(0.68, -0.6, 0.32, 1.6); */
Exit animations are faster than entrances. Use ~75% of enter duration.
CSS Animations
/* Prefer for simple, declarative animations */
- transitions for state changes
- @keyframes for complex sequences
- transform + opacity only (GPU-accelerated)
JavaScript Animation
/* Use for complex, interactive animations */
- Web Animations API for programmatic control
- Framer Motion for React
- GSAP for complex sequences
Performance
- GPU acceleration: Use
transform and opacity, avoid layout properties
- will-change: Add sparingly for known expensive animations
- Reduce paint: Minimize repaints, use
contain where appropriate
- Monitor FPS: Ensure 60fps on target devices
Accessibility
@media (prefers-reduced-motion: reduce) {
* {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
}
}
NEVER:
- Use bounce or elastic easing curves—they feel dated and draw attention to the animation itself
- Animate layout properties (width, height, top, left)—use transform instead
- Use durations over 500ms for feedback—it feels laggy
- Animate without purpose—every animation needs a reason
- Ignore
prefers-reduced-motion—this is an accessibility violation
- Animate everything—animation fatigue makes interfaces feel exhausting
- Block interaction during animations unless intentional
Verify Quality
Test animations thoroughly:
- Smooth at 60fps: No jank on target devices
- Feels natural: Easing curves feel organic, not robotic
- Appropriate timing: Not too fast (jarring) or too slow (laggy)
- Reduced motion works: Animations disabled or simplified appropriately
- Doesn't block: Users can interact during/after animations
- Adds value: Makes interface clearer or more delightful
Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.
1---2name: ui-animation3description: >-4 Adds purposeful animation to an existing feature: entrances, list add/remove, drag moves, state5 changes, hover and press feedback, with timing, easing and reduced-motion handling. Use when the6 UI feels static, dead or janky, items jump or teleport, or the user asks for transitions, motion7 or micro-interactions. Not for showpiece WebGL or scroll effects (use ui-advanced-effects).8version: 2.1.19user-invocable: true10argument-hint: "[target]"11metadata:12 source: https://skillmd.com/skills/the-utopia-studio/ui-animation13---1415Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.1617## MANDATORY PREPARATION1819Invoke /impeccable — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first. Additionally gather: performance constraints.2021---2223## Assess Animation Opportunities2425Analyze where motion would improve the experience:26271. **Identify static areas**:28 - **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)29 - **Jarring transitions**: Instant state changes that feel abrupt (show/hide, page loads, route changes)30 - **Unclear relationships**: Spatial or hierarchical relationships that aren't obvious31 - **Lack of delight**: Functional but joyless interactions32 - **Missed guidance**: Opportunities to direct attention or explain behavior33342. **Understand the context**:35 - What's the personality? (Playful vs serious, energetic vs calm)36 - What's the performance budget? (Mobile-first? Complex page?)37 - Who's the audience? (Motion-sensitive users? Power users who want speed?)38 - What matters most? (One hero animation vs many micro-interactions?)3940If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.4142**CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them.4344## Plan Animation Strategy4546Create a purposeful animation plan:4748- **Hero moment**: What's the ONE signature animation? (Page load? Hero section? Key interaction?)49- **Feedback layer**: Which interactions need acknowledgment?50- **Transition layer**: Which state changes need smoothing?51- **Delight layer**: Where can we surprise and delight?5253**IMPORTANT**: One well-orchestrated experience beats scattered animations everywhere. Focus on high-impact moments.5455## Implement Animations5657Add motion systematically across these categories:5859### Entrance Animations60- **Page load choreography**: Stagger element reveals (100-150ms delays), fade + slide combinations61- **Hero section**: Dramatic entrance for primary content (scale, parallax, or creative effects)62- **Content reveals**: Scroll-triggered animations using intersection observer63- **Modal/drawer entry**: Smooth slide + fade, backdrop fade, focus management6465### Micro-interactions66- **Button feedback**:67 - Hover: Subtle scale (1.02-1.05), color shift, shadow increase68 - Click: Quick scale down then up (0.95 → 1), ripple effect69 - Loading: Spinner or pulse state70- **Form interactions**:71 - Input focus: Border color transition, slight scale or glow72 - Validation: Shake on error, check mark on success, smooth color transitions73- **Toggle switches**: Smooth slide + color transition (200-300ms)74- **Checkboxes/radio**: Check mark animation, ripple effect75- **Like/favorite**: Scale + rotation, particle effects, color transition7677### State Transitions78- **Show/hide**: Fade + slide (not instant), appropriate timing (200-300ms)79- **Expand/collapse**: Height transition with overflow handling, icon rotation80- **Loading states**: Skeleton screen fades, spinner animations, progress bars81- **Success/error**: Color transitions, icon animations, gentle scale pulse82- **Enable/disable**: Opacity transitions, cursor changes8384### Navigation & Flow85- **Page transitions**: Crossfade between routes, shared element transitions86- **Tab switching**: Slide indicator, content fade/slide87- **Carousel/slider**: Smooth transforms, snap points, momentum88- **Scroll effects**: Parallax layers, sticky headers with state changes, scroll progress indicators8990### Feedback & Guidance91- **Hover hints**: Tooltip fade-ins, cursor changes, element highlights92- **Drag & drop**: Lift effect (shadow + scale), drop zone highlights, smooth repositioning93- **Copy/paste**: Brief highlight flash on paste, "copied" confirmation94- **Focus flow**: Highlight path through form or workflow9596### Delight Moments97- **Empty states**: Subtle floating animations on illustrations98- **Completed actions**: Confetti, check mark flourish, success celebrations99- **Easter eggs**: Hidden interactions for discovery100- **Contextual animation**: Weather effects, time-of-day themes, seasonal touches101102## Technical Implementation103104Use appropriate techniques for each animation:105106### Timing & Easing107108**Durations by purpose:**109- **100-150ms**: Instant feedback (button press, toggle)110- **200-300ms**: State changes (hover, menu open)111- **300-500ms**: Layout changes (accordion, modal)112- **500-800ms**: Entrance animations (page load)113114**Easing curves (use these, not CSS defaults):**115```css116/* Recommended - natural deceleration */117--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1); /* Smooth, refined */118--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1); /* Slightly snappier */119--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1); /* Confident, decisive */120121/* AVOID - feel dated and tacky */122/* bounce: cubic-bezier(0.34, 1.56, 0.64, 1); */123/* elastic: cubic-bezier(0.68, -0.6, 0.32, 1.6); */124```125126**Exit animations are faster than entrances.** Use ~75% of enter duration.127128### CSS Animations129```css130/* Prefer for simple, declarative animations */131- transitions for state changes132- @keyframes for complex sequences133- transform + opacity only (GPU-accelerated)134```135136### JavaScript Animation137```javascript138/* Use for complex, interactive animations */139- Web Animations API for programmatic control140- Framer Motion for React141- GSAP for complex sequences142```143144### Performance145- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties146- **will-change**: Add sparingly for known expensive animations147- **Reduce paint**: Minimize repaints, use `contain` where appropriate148- **Monitor FPS**: Ensure 60fps on target devices149150### Accessibility151```css152@media (prefers-reduced-motion: reduce) {153 * {154 animation-duration: 0.01ms !important;155 animation-iteration-count: 1 !important;156 transition-duration: 0.01ms !important;157 }158}159```160161**NEVER**:162- Use bounce or elastic easing curves—they feel dated and draw attention to the animation itself163- Animate layout properties (width, height, top, left)—use transform instead164- Use durations over 500ms for feedback—it feels laggy165- Animate without purpose—every animation needs a reason166- Ignore `prefers-reduced-motion`—this is an accessibility violation167- Animate everything—animation fatigue makes interfaces feel exhausting168- Block interaction during animations unless intentional169170## Verify Quality171172Test animations thoroughly:173174- **Smooth at 60fps**: No jank on target devices175- **Feels natural**: Easing curves feel organic, not robotic176- **Appropriate timing**: Not too fast (jarring) or too slow (laggy)177- **Reduced motion works**: Animations disabled or simplified appropriately178- **Doesn't block**: Users can interact during/after animations179- **Adds value**: Makes interface clearer or more delightful180181Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.