find-animation-opportunities

Scan a codebase for UI moments that would benefit from motion and propose exact animation recipes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often feel static or jarring because state changes, entrances, and interactions lack motion, yet adding animation everywhere makes products sluggish. This Skill audits a codebase or UI for the few places where animation genuinely helps and rejects everything else, producing precise, implementable motion recipes without touching source code. ## Core Features & Use Cases - Opportunity Sweep: Hunts known seams such as missing press feedback, teleporting conditional renders, panels with no spatial connection to their trigger, and flat empty or success states. - Four-Question Gate: Every candidate must pass frequency, purpose, speed, and function checks, so keyboard-driven or high-frequency interactions are rejected outright. - Exact Motion Recipes: Each suggestion includes concrete values such as transform: scale(0.97) with transition: transform 160ms ease-out, spring parameters, stagger timings, and reduced-motion handling. - Use Case: Ask it to review a React app's components and receive a ranked table of 5-7 animation opportunities with file:line evidence, plus a required list of rejected candidates explaining why they were excluded. ## Quick Start Ask the agent to find animation opportunities in this codebase and report the highest-leverage suggestions with exact values.

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 for known seams: pressable elements without :active states, conditional renders that appear instantly, popovers disconnected from their trigger, and flat empty or success states. Filter each candidate by how often users see it, since high-frequency interactions should never be animated.

What UI elements should never be animated?

Keyboard-initiated actions like command palettes and shortcuts used 100+ times per day should never animate, since motion makes them feel slow and delayed. Functional, information-dense UI such as data charts users are reading should also stay static.

Does this skill modify my source code to add animations?

No, it is strictly read-only and only reports opportunities with exact motion values. To implement a suggestion, hand the recipe to an implementation skill such as improve-animations or apply it manually.

What duration should UI animations use?

Press feedback runs 100-160ms, tooltips and small popovers 125-200ms, dropdowns 150-250ms, and modals or drawers 200-500ms. UI animation should stay under 300ms; only marketing or explanatory motion can run longer.

When is it appropriate to add delightful or bouncy animations?

Delight is only appropriate at rare, first-time moments like onboarding, empty states, success confirmations, and celebrations. At these low frequencies, bounce, generous staggers, and longer beats are welcome; everywhere else they hinder daily use.