find-animation-opportunities

Analyzes UI code to identify where motion would genuinely improve the interface.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often either lack motion where it would provide feedback and spatial continuity, or over-animate in ways that slow users down. This Skill audits existing UI code and produces a read-only report naming the few places motion would genuinely help, with exact values, plus what should stay static. ## Core Features & Use Cases - Candidate Sweep: Scans UI code for common motion gaps such as pressable elements with no :active state, instantly appearing dialogs, and popovers scaling from their own center. - Four-Question Gate: Filters every candidate through frequency, purpose, speed, and function checks, rejecting anything that fails, with a hard cap of 5-7 suggestions. - Structured Report: Outputs an opportunities table with file:line citations and exact values (curve, duration, transform, origin), a list of rejected candidates with reasons, and a final verdict. - Use Case: Point it at a React component library before a design polish sprint to get a prioritized, implementation-ready list of animation improvements without touching source code. ## Quick Start Ask the assistant to scan this UI codebase and report the few places where animation would genuinely improve it, with exact values and file references.

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 a UI?▼

Run this Skill against the UI codebase. It sweeps for common motion gaps like missing :active states and instantly appearing dialogs, filters candidates through a four-question gate, and returns a capped report with exact values and file:line citations.

What makes a good UI animation candidate?▼

A candidate must pass four checks: low enough frequency that motion will not become friction, a clear purpose such as feedback or spatial consistency, a duration fitting the element's speed budget, and a functional benefit rather than decoration.

Does this Skill modify my source code?▼

No. It is strictly read-only and never edits files, creates new files, or installs anything. Its only output is a report; implementation is delegated to separate skills like improve-animations or animate.

How many animation suggestions will I get?▼

At most 5-7 for a whole app, fewer for a single component. The Skill's value is in rejection: a run returning three suggestions and eight rejections is considered successful, while twenty suggestions indicates failure.

When should UI elements not be animated?▼

Elements used hundreds of times daily, like command palettes or keyboard navigation, should never be animated. Data-dense and information-critical UI also defaults to static, since motion between the user and their goal adds friction.