find-animation-opportunities

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often have jarring state changes, missing press feedback, or elements that teleport without transition, but adding animation indiscriminately makes products feel sluggish. This Skill sweeps a codebase for genuine animation opportunities, rejects candidates that should never animate, and reports precise motion recipes without touching source code. ## Core Features & Use Cases - Four-question gate: Every candidate is filtered by frequency, purpose, speed budget, and functional impact, so only high-conviction suggestions survive. - Exact motion recipes: Each suggestion includes concrete values such as cubic-bezier curves, durations in milliseconds, transform and opacity properties, plus reduced-motion handling. - Required rejection list: The report documents 2-5 considered-but-rejected candidates with the gate question that killed them, preventing over-animation. - Use Case: Ask it to review a Next.js app's components; it returns a table like "Toast.tsx:41 — toasts appear instantly — suggest @starting-style entry with translateY(100%), 400ms ease" ordered by leverage. ## Quick Start Ask the assistant to find animation opportunities in this repository and report the top 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?▼

Run this Skill against your codebase to sweep for feedback gaps, teleporting state, missing spatial stories, and gesture seams. It returns an ordered table of at most 5-7 suggestions, each with file:line evidence and exact motion values.

What UI elements should never be animated?▼

Keyboard-initiated, high-frequency actions like command palettes and shortcuts should never animate, since they run 100+ times per day and motion makes them feel slow. Functional data displays like analytics charts also reject decorative motion.

Does this Skill modify my source code?▼

No, it is strictly read-only. It reports suggestions with exact values and hands implementation off to other skills like improve-animations, never editing files itself.

What animation duration should UI transitions use?▼

The Skill enforces budgets under 300ms for standard UI: 100-160ms for press feedback, 125-200ms for tooltips, 150-250ms for dropdowns, and 200-500ms for modals and drawers. Suggestions failing these budgets are rejected.

When should I use review-animations instead of this Skill?▼

Use review-animations to critique existing animations and improve-animations to plan fixes for them. This Skill only finds places with no animation that should have one.