Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When a user submits animation or motion code (a diff, component, or PR) and asks for a craft review, or an agent needs to validate motion quality before approval. General code review requests are declined.
A rigorous motion review: specific file:line findings, prioritized impact tiers, and an explicit Block/Approve decision that enforces a high craft bar derived from Emil Kowalski's philosophy.
Use Cases
A frontend developer opens a PR that adds a dropdown and a toast. They invoke review-animations to check the diff. The skill flags `ease-in` on the dropdown, `scale(0)` entrance, and non-interruptible keyframes on the toast, then outputs a Before/After table and a Block verdict with file:line citations. This prevents low-craft motion from reaching users and gives clear fix directions.
A design engineer audits a dashboard's existing motion for quality. They paste the animation CSS into review-animations. The skill identifies animations on 100+/day keyboard actions, missing reduced-motion, and layout-property animation, proposing deletions and GPU moves via the remedial hierarchy. The team ships a crisper, accessible interface with justified motion only.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
