framer-motion

framer-motion

Create smooth, performant animations with framer-motion. Use when building page transitions, component animations, or gesture-based interactions.

1星標
0分支
更新於 1/24/2026
SKILL.md
readonlyread-only
name
framer-motion
description

Create smooth, performant animations with framer-motion. Use when building page transitions, component animations, or gesture-based interactions.

Framer Motion Skill

When to use

  • Adding page transitions or route animations.
  • Creating component enter/exit animations.
  • Building gesture interactions (drag, hover, tap).
  • Animating lists with stagger effects.

Guardrails

  • Keep animations under 300ms for snappiness.
  • Always respect prefers-reduced-motion.
  • Use variants for complex, coordinated animations (not inline).
  • Animate transform/opacity only (avoid layout thrash).

Workflow checklist

  1. Identify what should animate and when (mount, route change, user interaction).
  2. Define variants for multi-state animations (initial, animate, exit).
  3. Use motion components (motion.div, motion.span) for animated elements.
  4. Coordinate children with staggerChildren in parent variants.
  5. Test with reduced motion to ensure accessible fallbacks.

Common patterns

Page transitions

import { motion } from 'framer-motion'

export function PageTransition({ children }: { children: React.ReactNode }) {
  return (
    <motion.div
      initial={{ opacity: 0, y: 20 }}
      animate={{ opacity: 1, y: 0 }}
      exit={{ opacity: 0, y: -20 }}
      transition={{ duration: 0.3 }}
    >
      {children}
    </motion.div>
  )
}

Stagger children

const container = {
  hidden: { opacity: 0 },
  show: {
    opacity: 1,
    transition: {
      staggerChildren: 0.1
    }
  }
}

const item = {
  hidden: { opacity: 0, y: 20 },
  show: { opacity: 1, y: 0 }
}

<motion.div variants={container} initial="hidden" animate="show">
  {items.map(item => (
    <motion.div key={item.id} variants={item}>
      {item.content}
    </motion.div>
  ))}
</motion.div>

Best practices

  • ✅ Use variants for readability and reusability
  • ✅ Keep duration under 300ms for UI responsiveness
  • ✅ Animate transform/opacity (GPU-accelerated)
  • ✅ Add layout prop for automatic layout animations
  • ❌ Don't animate width/height directly (causes layout thrash)
  • ❌ Don't nest many motion components (performance)

References

  • Library patterns: docs/dev-1/docs/16-library-patterns.md#framer-motion
  • Design system: docs/dev-1/docs/13-unified-design-system.md (animation tokens)

Tooling

  • Use Context7 or web search for framer-motion API details when needed.

You Might Also Like

Related Skills

cache-components

cache-components

137Kdev-frontend

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

vercel avatarvercel
獲取
component-refactoring

component-refactoring

128Kdev-frontend

Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.

langgenius avatarlanggenius
獲取
web-artifacts-builder

web-artifacts-builder

47Kdev-frontend

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

anthropics avataranthropics
獲取
frontend-design

frontend-design

47Kdev-frontend

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

anthropics avataranthropics
獲取
react-modernization

react-modernization

28Kdev-frontend

Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.

wshobson avatarwshobson
獲取
tailwind-design-system

tailwind-design-system

28Kdev-frontend

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

wshobson avatarwshobson
獲取