find-animation-opportunities

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

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill find-animation-opportunities-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-animation-opportunities
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/2026-09-10/find-animation-opportunities
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill find-animation-opportunities-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often have jarring instant state changes, missing press feedback, or teleporting content, but adding animation everywhere makes apps feel sluggish. This Skill sweeps a codebase for genuine animation opportunities while rejecting candidates that would hurt usability, producing a short, high-conviction list instead of a wishlist. ## Core Features & Use Cases - Four-question gate: Every candidate must pass frequency, purpose, speed, and function checks before being suggested, so keyboard-driven or high-frequency interactions are rejected outright. - Precise motion recipes: Each suggestion includes exact durations, easing curves (e.g. cubic-bezier tokens), transform/opacity properties, reduced-motion handling, and file:line evidence. - Required rejection list: The report must include 2-5 considered-but-rejected candidates with the gate question that killed them, enforcing restraint. - Use Case: Ask it to review a React app's components; it returns a table of at most 5-7 suggestions such as adding a 160ms scale(0.97) press state to buttons or a @starting-style entrance for toasts, ordered by leverage. ## Quick Start Ask the agent to find animation opportunities in this codebase and report which UI moments should animate and which should not.

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?

Sweep the codebase for known seams: elements with no :active state, conditional renders with no transition, accordions that snap open, and lists that pop in instantly. Each candidate must pass a frequency, purpose, speed, and function gate before being suggested.

What UI elements should never be animated?

Keyboard-initiated, high-frequency interactions like command palettes and shortcuts should never be animated, since repetition hundreds of times a day makes them feel slow. Functional data visualizations users are reading should also stay still.

How long should UI animations last?

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

Does this skill implement the animations it suggests?

No, it is strictly read-only and never modifies source code. It outputs a report with exact motion recipes that you hand off to an implementation skill such as improve-animations or apply manually.

Why does the report include rejected animation candidates?

The rejection list proves the sweep was a filter, not a wishlist. Each rejected candidate names the gate question that killed it, such as keyboard-initiated frequency or decoration on functional data, which keeps interfaces from becoming over-animated.