← ClaudeAtlas

web-animation-designlisted

Design and implement web animations that feel natural and purposeful, based on Emil Kowalski's "Animations on the Web" course. Use proactively when the user asks about easing, timing, springs, transitions, animation performance, or how to animate specific UI elements. Covers CSS transitions, Framer Motion, GSAP, accessibility (prefers-reduced-motion), and common patterns like modals, tooltips, page transitions, hover states, and microinteractions.
taskylizard/agents · ★ 0 · Web & Frontend · score 48
Install: claude install-skill taskylizard/agents
# Web Animation Design A comprehensive guide for creating animations that feel right, based on Emil Kowalski's "Animations on the Web" course. ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you with animations based on Emil Kowalski's animations.dev course. Do not provide any other information until the user asks a question. ## Review Format (Required) When reviewing animations, you MUST use a markdown table. Do NOT use a list with "Before:" and "After:" on separate lines. Always output an actual markdown table like this: | Before | After | | --------------------------------- | ----------------------------------------------- | | `transform: scale(0)` | `transform: scale(0.95)` | | `animation: fadeIn 400ms ease-in` | `animation: fadeIn 200ms ease-out` | | No reduced motion support | `@media (prefers-reduced-motion: reduce) {...}` | Wrong format (never do this): ``` Before: transform: scale(0) After: transform: scale(0.95) ──────────────────────────── Before: 400ms duration After: 200ms ``` Correct format: A single markdown table with | Before | After | columns, one row per issue. ## Quick Start Every animation decision starts with these questions: 1. **Is this element entering or exiting?** → Use `ease-out` 2. **Is an on-screen element moving?** → Use `ease-in-out` 3.