Audit a frequently used action
Show an interaction users repeat many times, such as choosing rows. Check whether animation delays the action and flag motion whose purpose no longer justifies its frequency.
Review a specific interaction before merging it. Inspect the code and observed behavior, then report which changes would improve timing, interruption or accessibility.
Give the agent changed files and a motion scenario, then ask for evidence-backed findings.
Provide files, reproduction steps, browser and accessibility states.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatPreview and copy the request. It is not sent automatically from this page.
Reference: Review Animations https://github.com/emilkowalski/skills/blob/main/skills/review-animations/SKILL.md Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Run Review Animations on my modal transition. Inspect opening, rapid close and reopen, and reduced motion. Give prioritized findings with file references and reproduce each issue before proposing a fix. Expected deliverable: A prioritized critique with reproduction and follow-up checks.
Emil Kowalski’s MIT-licensed Skill directs an agent to explicitly review animation code. It evaluates why motion exists, how often it runs, and how it behaves across interruption, reduced motion and hover-capable devices. Use the broader Design Engineering guide for a review that also covers layout, spacing, or interaction design.
Review one interaction in its real states before attempting a broad polish pass. Trace reported issues to a file, reproduction or measured symptom.
Show an interaction users repeat many times, such as choosing rows. Check whether animation delays the action and flag motion whose purpose no longer justifies its frequency.
Reproduce opening and dismissing a sheet in quick succession. Inspect the transition code and report any jump when a new animation begins before the previous one settles.
Enable the operating system or browser preference for reduced motion. Compare visible movement and preserved state feedback, and note the exact component that needs a fallback.
Provide a representative device and the transition to inspect. Use code or browser evidence to separate a suspected layout cost from a measured frame-rate issue.
Provide the changed components and the interaction you want to inspect. The review should connect each issue to visible behavior and a concrete correction.
Name the Skill and supply the animation code, component state and intended audience.
Check purpose, timing, repeated use, interruption, motion preferences and any available performance evidence.
Rank each issue, cite the code or reproduction and describe how a developer can verify the correction.
Read another Skill guide and check its original source before using it.