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 the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes across a codebase rather than a review of a single diff.
A prioritized audit table and self-contained implementation plans (exact values, paths, code) that zero-context agents can execute to improve motion craft.
Use Cases
A product team feels their dashboard app's interactions are sluggish and inconsistent. They invoke improve-animations to recon the stack, audit all motion code against craft rules, and receive a prioritized table of findings plus self-contained plans. Cheaper agents then execute the plans, improving easing, durations, and interruptibility without the team doing manual motion design.
A startup wants to add delight to a consumer app but lacks motion expertise. Using improve-animations with a category focus or deep effort, they get missed-opportunity suggestions and exact plans (cubic-bezier, spring configs) for states that should animate. Executors implement them in isolated worktrees, then review-animations checks the diff, raising perceived polish cheaply.
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
