agentleFS
ahonnahonn/dotfiles/.claude/skills/review-animations/SKILL.md

review-animations

Skill62 starsChanged 2 months agoMITView on GitHub

Audit animation and gesture changes for behavioral defects, accessibility, performance, and visual coherence.

98 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pick-ui-library, animate-expo and 6 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

    animate-expo

    Also in 22 projects that use this

  • sanmidableSkill

    write-swift

    Also in 24 projects that use this

  • jtfasulo7Skill

    animation-performance

    Apply when building scroll-scrubbed animations, marquees, continuous SVG/canvas animations, or fixing reports of "laggy", "stuttering", "doesn't render", "disappears and reappears", "jumps". Encodes the perf rules learned from the realtor-website rebuild.

    Also in 15 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

  • +2 more from sanmidable

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 96 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:

    Check touch, hover, and keyboard access where the changed interaction uses them.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 96 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

Reviewing Animations

Review motion in the requested scope against a high craft bar. Follow the user's requested review scope and output format; for a mixed review, apply this method to the motion portion and use the appropriate method for the remaining code.

Review method

  1. Identify affected interactions, target platform, input modes, motion primitives, and existing product tokens. Inspect surrounding lifecycle code as needed.
  2. Trace entry, exit, cancellation, reversal, repeated input, and cleanup. Check accessibility equivalents and whether motion delays functional input.
  3. Observe the interaction when tools and runtime are available. Profile suspected rendering problems under representative load. Code inspection can prove a stale callback or missing cancellation path; it cannot establish subjective feel or actual dropped frames on its own.
  4. Report the smallest useful findings with location, trigger, impact, evidence, and a concrete correction. Do not manufacture findings to earn an approval verdict.

Standards with context

  • Purpose and frequency: repeated actions should remain ready for immediate input. Keyboard-triggered motion is not automatically a defect.
  • Response and timing: judge first feedback, readiness, and settling separately. Roughly 300 ms is a useful tuning reference for small UI, not a universal ceiling. Built-in easing, accelerating exits, and symmetric timings can be appropriate.
  • Spatial coherence: scaling anchored overlays should communicate their source. Centered modals, fades, deliberate morphs, and icon effects have different needs; neither pure fade nor scale(0) is automatically a violation.
  • Interruptibility: prove that reversal starts from a coherent visible state and that completion callbacks cannot corrupt newer state. Judge behavior rather than banning keyframes or assuming every spring preserves velocity.
  • Rendering: prefer transform and opacity where they preserve intended behavior. Layout animation, clipping, blur, and library shorthand properties are investigation leads, not proof of poor performance. Check the installed version and target.
  • Accessibility: honor the relevant platform's reduced-motion setting while keeping state changes, focus, and functionality intact. Static transitions are valid. Check touch, hover, and keyboard access where the changed interaction uses them.
  • Cohesion: compare with surrounding product behavior. Blur, bounce, stagger, asymmetric timing, and custom curves are optional design choices.

CSS properties, browser compositing, media queries, and Pointer Events apply to web implementations. Do not apply them directly to React Native, Reanimated, or SwiftUI; inspect that platform's drivers, gesture lifecycle, and accessibility APIs instead.

References

STANDARDS.md routes to shared references by topic. Read only the reference needed for the interaction or finding. Tuning values support reasoning; they are not external requirements or substitutes for observed evidence.

Report and verdict

Separate these categories, omitting empty ones:

  • Defects: reproducible or code-provable failures, with severity proportional to user impact. Include file/line, trigger, evidence, and a targeted fix.
  • Design preferences: alternatives that may improve feel or consistency; explain the tradeoff without treating a house-style preference as a blocking bug.
  • Needs visual verification: an unresolved concern with a specific scenario and check. State which environment or observation is missing.

Lead with material findings and end with a scoped conclusion: block for established material defects; approve when the inspected scope has no material findings; use a qualified conclusion when essential visual or device evidence is unavailable. State what was verified and what was not. Do not claim runtime verification from source inspection or require a findings table when prose is clearer.

Choose remedies by the demonstrated problem: remove unnecessary delay, reduce motion, correct lifecycle or origin, improve rendering, or add missing accessibility handling. Treat accessibility defects according to impact, not as final cosmetic polish. Do not add effects or rewrite unrelated components during a review unless the user also requested implementation.

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.