motion-design
Applies motion design principles to create emotionally-driven, technically sound animations and transitions. Provides timing, easing, choreography, and Disney animation principles adapted for UI. Use when creating animations, transitions, micro-interactions, loading states, page transitions, scroll-triggered effects, or any motion work. Works with CSS, Framer Motion, GSAP, Lottie, Spring, or any animation system.
What this skill does
# Motion Design Skill ## When to Apply Use this skill when: - Creating UI animations (buttons, cards, modals, page transitions) - Designing micro-interactions and feedback animations - Building loading, success, or error states - Animating illustrations or decorative elements - Planning scroll-triggered or progress-based animations - Establishing brand motion identity - Choreographing multi-element sequences **Decision tree:** 1. Does it serve a functional purpose (feedback, guidance)? → Timing rules for responsiveness 2. Does it express brand personality? → Motion Personality archetypes 3. Does it tell a story or guide attention? → Disney principles + choreography 4. Is this a complex multi-element scene? → 1/3 Rule + stagger patterns --- ## Quick Reference: 8-Step Checklist Before creating any animation: 1. **Emotional target?** — joy, calm, urgency, elegance 2. **Motion Personality?** — Playful, Premium, Corporate, Energetic 3. **Primary property?** — position, scale, rotation, opacity 4. **Duration?** — see duration table below 5. **Easing family?** — entrance=decelerate, exit=accelerate 6. **Hero element?** — apply staging principles 7. **Secondary + ambient layers?** — add richness 8. **1/3 rules?** — motion distance, simultaneous elements --- ## Three Pillars (CRITICAL) Every animation must satisfy three pillars before any technical decisions: | Pillar | Question | Drives | |--------|----------|--------| | **Emotional Intent** | What should the viewer FEEL? | Easing, timing, amplitude | | **Visual Narrative** | What's the micro-story? | Setup → Action → Resolution | | **Motion Craft** | How do we make it believable? | Physics, secondary motion, paths | **Three motion layers** (flat animation = missing layers): - **Primary**: Main action the viewer follows - **Secondary**: Supporting richness (shadows, icons shifting) - **Ambient**: Background life (gradients, subtle pulses) > Deep dive: [director/core-philosophy.md](director/core-philosophy.md) --- ## Motion Personality Select ONE archetype per project. Apply consistently. | Archetype | Duration | Easing | Overshoot | Keywords | |-----------|----------|--------|-----------|----------| | **Playful** | 150-300ms | ease-out-back | 10-20% | fun, whimsical, bouncy, cute | | **Premium** | 350-600ms | cubic-bezier(0.4,0,0.2,1) | 0% | elegant, minimal, luxury, sophisticated | | **Corporate** | 200-400ms | cubic-bezier(0.2,0,0,1) | 0-3% | clean, professional, business, dashboard | | **Energetic** | 100-250ms | ease-out-expo | 15-30% | dynamic, energetic, bold, exciting | **Default**: Corporate for UI, Playful for illustrations. **Brand Motion Identity** — define three constants: 1. **Signature easing**: One curve for 80% of animations 2. **Duration palette**: 3 durations (quick / standard / slow) 3. **Entrance pattern**: One consistent entry style > Deep dive: [director/motion-personality.md](director/motion-personality.md) --- ## Property Selection | Effect Goal | Primary Property | Secondary Properties | |-------------|------------------|---------------------| | Entrance/Exit | position | opacity, scale | | Emphasis/Attention | scale | rotation (subtle), opacity pulse | | State Change | opacity, color | scale (press feedback) | | Direction/Flow | position | rotation (follow path) | | Depth/3D Feel | scale + shadow | position (parallax) | | Loading/Progress | rotation (spinner) | scale, opacity pulse | | Success | scale (pop) | color, rotation (checkmark draw) | | Error/Alert | position (shake) | color, rotation (wobble) | **Simplicity threshold**: Use the minimum properties needed. One = direct. Two = polished. Three+ = potentially overwhelming. > Deep dive: [reference/property-selection.md](reference/property-selection.md) --- ## Duration Table | Element Type | Duration | Rationale | |-------------|----------|-----------| | Tooltip / micro-feedback | 80-120ms | Must feel instant | | Button press / toggle | 120-180ms | Responsive feedback | | Icon transition | 150-250ms | Clear state change | | Card enter / exit | 200-350ms | Spatial awareness | | Modal / dialog | 300-400ms | Focus shift | | Page transition | 400-600ms | Context switch | | Dramatic reveal | 600-1200ms | Theatrical build | **Distance scales duration**: 100px = base. 200px = 1.3x. 400px = 1.6x. **Enter > Exit**: Entrances 30-50% longer than exits. Users care about what appears. **Interactive feedback**: - Hover: <100ms - Press: <150ms - Release/settle: 200-300ms - Error shake: 300-400ms (2-3 oscillations) > Deep dive: [reference/timing-easing-tables.md](reference/timing-easing-tables.md) --- ## Easing Selection **Directional rules**: - **Entrance** → decelerate (fast start, gentle landing): ease-out family - **Exit** → accelerate (gentle start, fast departure): ease-in family - **On-screen** → smooth both ends: ease-in-out family - **Looping ambient** → seamless: sine-based ease-in-out **Industry standards**: | Standard | Cubic Bezier | Use For | |----------|-------------|---------| | Material Design 3 | (0.2, 0, 0, 1) | Default on-screen | | MD3 Emphasized | (0.05, 0.7, 0.1, 1) | Entrances, attention | | MD3 Accelerate | (0.3, 0, 1, 1) | Exits, dismissals | | Apple HIG | (0.25, 0.1, 0.25, 1) | Standard iOS | | Snappy UI | (0.2, 0, 0, 1) | Fast, decisive | | Gentle float | (0.4, 0, 0.2, 1) | Ambient, background | | Bounce settle | (0.175, 0.885, 0.32, 1.275) | Overshoot, playful | **Material-based easing**: | Material | Duration Scale | Overshoot | |----------|---------------|-----------| | Rigid (metal, stone) | 1.2x | 0% | | Elastic (rubber, gel) | 0.8x | 15-25% | | Fluid (water, paint) | 1.5x | 5% | | Paper (cards, sheets) | 1.0x | 3-5% | | Gas (smoke, fog) | 2.0x | 0% | | Glass (brittle) | 0.9x | 0% | > Deep dive: [reference/timing-easing-tables.md](reference/timing-easing-tables.md) --- ## Common Patterns ### Button Press (Playful) 1. **Anticipation**: Scale to 0.97 (50ms, ease-out) 2. **Squash**: Scale to [1.04, 0.96] (100ms, ease-in) 3. **Follow through**: Overshoots to 1.02, settles to 1.0 (spring, 200ms) 4. **Secondary**: Shadow shrinks during press, icon shifts down 2px 5. **Total**: ~150ms press + 200ms settle ### Card Entrance (Premium) 1. **Start**: 20px below target, opacity 0 2. **Path**: Slight curve (10px X offset at midpoint) 3. **Easing**: ease-out-cubic deceleration 4. **Follow through**: Shadow arrives 50ms after card 5. **Secondary**: Content fades in 100ms after card lands 6. **Staging**: Other cards dim to 80% ### Success State (Playful) 1. **Primary**: Scale pop with ease-out-back 2. **Secondary**: Checkmark draws in 3. **Ambient**: Subtle particle burst 4. **Color**: Green fill 5. **Total**: 300-400ms ### Error Shake (Corporate) 1. **Primary**: Position oscillates 2-3 times, ±10-15px horizontal 2. **Easing**: ease-in-out for sharp stops 3. **Color**: Red tint 4. **Total**: 300-400ms 5. **No overshoot**: Errors feel firm > More patterns: [patterns/entrance-exit.md](patterns/entrance-exit.md) | [patterns/state-feedback.md](patterns/state-feedback.md) --- ## Choreography Essentials **Coordinated entry**: - Lead with the hero — primary element enters first or most prominently - Spatial consistency — all elements enter from same direction - Counter-motion — hero moves right → ambient moves left at 20-30% speed **1/3 Rule (distance)**: No motion travels more than 1/3 of screen without a keyframe change. **1/3 Rule (elements)**: With 3+ elements, no more than 1/3 in active motion simultaneously. **Stagger budgets**: | Pattern | Delay | Total Budget | Use Case | |---------|-------|-------------|----------| | Micro cascade | 20-40ms | <200ms | List items, grid cells | | Standard | 50-100ms | <400ms | Cards, panels, nav | | Dramatic | 100-200ms | <600ms | Hero sections | | Wave | 30-60ms | <500ms | Data visualizations | **Critical**: Total stagger must stay under 500ms. > Deep dive: [director/choreography.md](director/choreography.md) --- ## Emotion-to-Motion
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.