improve-animations

Audit a codebase's motion and write prioritized, self-contained animation fix plans.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill improve-animations-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-animations
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/improve-animations
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill improve-animations-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Whole-app motion quality is hard to assess: animations are scattered across CSS, Framer Motion variants, and gesture handlers, and fixing them ad hoc produces inconsistent easing, janky performance, and false positives on legitimate spring physics. This Skill surveys every animation in a codebase, vets each finding against the actual source, and produces a prioritized audit plus self-contained implementation plans that any agent can execute. ## Core Features & Use Cases - Four-phase read-only workflow: recon the motion stack and gesture surfaces, audit against eight categories (easing, duration, performance, accessibility, cohesion, and more), vet every finding at its file:line, then write plans — it never modifies source code. - Two-register motion judgment: distinguishes presentation surfaces (where overshoot and springs are findings) from gesture surfaces like drag sheets, swipes, and voice barge-in (where springs are correct), preventing the most common false positive in motion audits. - Self-contained execution plans: each plan inlines exact file paths, current-code excerpts, target token values, and feel-checks so a less-capable agent can execute it with zero prior context. - Use Case: Ask it to audit a Next.js + Framer Motion dashboard that feels sluggish; it flags an animated command palette and an ease-in dropdown as HIGH-severity findings, correctly leaves the drag sheet's spring alone, and writes ordered fix plans under plans/. ## Quick Start Ask the agent to audit the animations across this whole app and produce a prioritized roadmap of motion fixes.

Frequently Asked Questions about improve-animations

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

FAQPage Schema
How do I audit all animations in a codebase at once?

Run a four-phase pass: recon the motion stack and gesture surfaces, audit against eight categories like easing, performance, and accessibility, vet each finding by re-reading its file:line, then write one self-contained plan per selected finding. The process is read-only and never edits source.

When should I use a motion audit instead of fixing one animation?

Use a whole-app audit when the ask zooms out — 'improve the animations', 'the app feels janky', or a roadmap of fixes. For building or fixing a single animation now, use a motion-crafting skill that writes the CSS, GSAP, or Framer Motion code directly.

Does this work with Framer Motion, GSAP, and plain CSS?

Yes. The recon phase detects Framer Motion, Motion, GSAP, React Spring, plain CSS, and WAAPI, plus Tailwind motion config and component libraries like Radix or shadcn/ui, and audits whatever stack it finds.

Why is a spring animation sometimes correct and sometimes a bug?

It depends on the register. On gesture surfaces where a finger or voice drives the element in real time — drag sheets, swipes, pull-to-refresh — springs and velocity carry are correct. On presentation surfaces like entrances and dropdowns, overshoot is a finding.

Can the audit modify my source code to fix issues?

No. The audit is strictly read-only on source; its only writes are plan files under plans/. Each plan is self-contained with exact paths, code excerpts, and target values so any agent can execute it separately.

When should I not run a whole-app motion audit?

Skip it on tiny or brand-new apps with almost no motion to survey — a three-screen prototype with two fades has nothing to audit. Also skip it for single-diff reviews, mechanical fps measurement, or verdicts on whether finished motion is ready to ship.