agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/improve-animations/SKILL.md

improve-animations

Skill4 starsChanged 11 days agoMITView on GitHub

Audit existing web UI motion and prioritize concrete improvements or self-contained implementation plans. Use for a motion roadmap; animate owns implementation and diff review.

68 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pick-ui-library, write-swift and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • cal1888Skill

    pick-ui-library

    Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.

    Also in 43 projects that use this

  • sanmidableSkill

    write-swift

    Also in 24 projects that use this

  • sanmidableSkill

    animate-expo

    Also in 21 projects that use this

  • AnasX7Skill

    explain-interface

    Helps you figure out how something was built on the web.

    Also in 3 projects that use this

  • desktop-commanderSkill

    extract-design-system

    Extract design primitives from a public website and generate starter token files for your project.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When plans are requested, make each independently executable: current revision, problem/current excerpt, exact targets and token values, …

    line 26

“Common” is measured: kept by at least 6 in 10 of the 66 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find the highest-value fixes in motion that should remain. Adapted from Emil Kowalski; source and compatibility. Audit/plan requests return findings without source edits. Save plans only when requested. Explicit implementation requests continue through animate and the project's delivery gates, in the current context; no automatic executors, agents or worktrees.

Audit

  1. Map the requested surface, installed motion library/version, component primitives, existing tokens, input paths and product context. Identify expected frequency without inventing usage counts. Respect documented tradeoffs; confirm each cited location.
  2. Load animate and its craft reference. Audit purpose/frequency, easing/duration, physicality/origin, interruption, rendering cost, accessibility, token cohesion and genuine missed opportunities. Apply these axes inline. For unnecessary motion, route to remove-animations rather than polishing it.
  3. Vet findings against actual state changes and existing decisions. Distinguish reproducible defects from craft suggestions and unmeasured performance suspicions. Rank by user impact and effort; show severity, category, file:line, evidence and fix. An empty result is valid; do not force additions or fixed finding counts.
  4. When plans are requested, make each independently executable: current revision, problem/current excerpt, exact targets and token values, repository exemplar, ordered edits, scope/dependencies, rollback and focused verification commands. Include rapid reversal, keyboard/touch, reduced motion and a real feel-check; name any device evidence still needed. Revalidate stale plans against current code.

For the sequence remove-animations -> improve-animations -> animation-performance, subtract first, assess retained motion second, then profile the remaining frame problems. The sequence preserves the requested endpoint; an audit does not authorize fixes.

Load animation-performance for frame bottlenecks; static code inspection cannot prove smoothness. Load dependencies through the dependency-loading contract.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free