find-animation-opportunities

Scans a codebase for UI moments that would benefit from motion and proposes exact animation recipes.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/squidllee/skills --skill find-animation-opportunities-squidllee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-animation-opportunities
Source: https://github.com/squidllee/skills/tree/main/find-animation-opportunities
Command: npx skills add https://github.com/squidllee/skills --skill find-animation-opportunities-squidllee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often feel static or jarring because state changes, entrances, and feedback moments lack motion, yet adding animation everywhere makes products feel sluggish. This Skill sweeps a codebase for the few moments that genuinely deserve animation and rejects everything else, so you get a short, high-conviction list instead of an over-animated wishlist. ## Core Features & Use Cases - Opportunity sweep: Hunts known seams such as missing :active press feedback, teleporting conditional renders, accordions that snap open, popovers with no spatial connection to their trigger, and gesture handlers without spring physics. - Four-question gate: Every candidate must pass frequency, purpose, speed, and function checks, with keyboard-initiated and 100+/day interactions rejected outright. - Precise recipes: Each suggestion includes exact durations, cubic-bezier easing tokens, transform/opacity properties, reduced-motion handling, and file:line evidence, plus a required list of rejected candidates. - Use Case: Ask it to review a settings page or dashboard, and receive a table of 5-7 ordered suggestions like "Toast.tsx:41 — enter via @starting-style with opacity and translateY(100%), 400ms ease" along with the verdict on how much motion the interface actually needs. ## Quick Start Ask the assistant to find animation opportunities in this codebase and report which UI moments should and should not be animated.

Frequently Asked Questions about find-animation-opportunities

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find where to add animations in my web app?▼

Run this Skill against your codebase to sweep for known opportunity seams: missing :active press states, conditional renders with no transition, accordions that snap open, and popovers disconnected from their triggers. It returns an ordered table of at most 5-7 suggestions with exact durations and easing values.

What UI elements should never be animated?▼

Keyboard-initiated and very high-frequency interactions should never be animated, including command palettes, keyboard shortcuts, and focus jumps used 100+ times per day. Functional data visualizations users are actively reading should also stay static, since decoration hinders comprehension.

Does this Skill implement the animations it suggests?▼

No, it is strictly read-only and never modifies source code. Each suggestion includes exact values you can hand to a developer or pass to a companion skill like improve-animations to generate an implementation plan.

How long should UI animations last?▼

Standard budgets keep UI animation under 300ms: press feedback at 100-160ms, tooltips and small popovers at 125-200ms, dropdowns at 150-250ms, and modals or drawers at 200-500ms. Only marketing or explanatory motion may run longer.

Why does the report include rejected animation candidates?▼

The rejected list proves the sweep was a filter, not a wishlist. Each rejection names the gate question that killed it, such as frequency or function, so you can trust the surviving suggestions are high-conviction rather than decorative.