adding-animations
Phase 4: ADDING ANIMATIONS — Motion, states, and visual effects
When
After Phase 3 components are generated. Before design audit.
Input (from Phase 3)
- Generated HTML/CSS components with variants and layouts.
- Motion personality from
design-system.md(corporate / modern / playful / luxury).
Steps
- Read motion personality from
design-system.md— determines timing, easing, and intensity. - Entrance animations — EVERY section must animate on scroll (IntersectionObserver). Stagger children by 80-120ms. Use fadeUp (translateY 30px→0) + fadeIn (opacity 0→1). Cards stagger in grid order.
- Hover depth — buttons: translateY(-3px) + shadow-lg + brightness(1.05). Cards: translateY(-8px) + shadow-xl + scale(1.01). Links: color transition 150ms.
- Focus/disabled — :focus-visible with 2px outline + 4px offset. :disabled with opacity 0.4 + cursor not-allowed. MANDATORY on all interactive elements.
- Visual layers — glassmorphism on nav (backdrop-blur 12px + bg oklch/0.85). Hero gradient overlay (oklch dark/0.6→transparent). Section separators (clip-path polygon or SVG wave). Background gradient orbs (radial-gradient oklch with blur).
- Micro-interactions — button press scale(0.97), toggle slide 200ms, form input focus border-color transition, loading skeleton pulse animation.
- Add page transitions from
references/page-transitions.md— route-level animations. - Implement — Use
mcp__gemini-design__modify_frontendto inject Framer Motion code into existing components. - Validate accessibility —
prefers-reduced-motionsupport required. Timing limits: hover <100ms, modal <300ms, page <400ms (seereferences/motion-principles.md).
Output
- All components animated with Framer Motion matching the motion personality.
- Interactive states (hover, focus, active, disabled, loading) on every interactive element.
- Visual effects applied where allowed. Reduced-motion fallbacks included.
Next → Phase 5: DESIGN AUDIT
5-design-audit/SKILL.md — Audit visual consistency, accessibility, and anti-AI-slop.
References
| File | Purpose |
|---|---|
references/motion-patterns.md |
Core Framer Motion patterns |
references/motion-principles.md |
Timing limits and principles |
references/entrance-patterns.md |
Entrance animation patterns |
references/interactive-states-ref.md |
State definitions (hover, focus, etc.) |
references/micro-interactions.md |
Micro-interaction patterns |
references/glassmorphism-advanced-ref.md |
Glassmorphism techniques |
references/layered-backgrounds-ref.md |
Layered background effects |
references/page-transitions.md |
Route-level transitions |
references/patterns-cards.md |
Card animation patterns |
references/patterns-buttons.md |
Button animation patterns |
references/patterns-navigation.md |
Navigation animations |
references/patterns-microinteractions.md |
Detail micro-interactions |
references/reduced-motion.md |
prefers-reduced-motion a11y patterns |
More from fusengine/agents
laravel-architecture
Design Laravel app architecture with services, repositories, actions, and clean code patterns. Use when structuring projects, creating services, implementing DI, or organizing code layers.
97laravel-blade
Create Blade templates with components, slots, layouts, and directives. Use when building views, reusable components, or templating.
88laravel-livewire
Livewire 3 reactive components - wire:model, actions, events, Volt, Folio. Use when building reactive UI without JavaScript.
86nextjs-i18n
Next.js 16 internationalization with next-intl or DIY. Use when implementing i18n, translations, localization, multilingual, language switch, locale routing, or formatters.
59solid-php
SOLID principles for Laravel 12 and PHP 8.5. Files < 100 lines, interfaces separated, PHPDoc mandatory. Auto-detects Laravel and FuseCore architecture.
51tailwindcss-v4
Tailwind CSS v4.1 core features, @theme, directives, migration guide
46