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 asks "what could be animated here?" or wants to "make this feel more alive" on a codebase or UI, and no existing animation needs fixing.
A read-only report proposing precise, restrained motion recipes (not implementation), helping teams add only high-leverage animation where it truly helps.
Use Cases
A product designer reviews a newly built dashboard and feels it is static. They invoke the skill to sweep the code for missing motion. The skill rejects high-frequency keyboard actions, and proposes only 3 subtle opportunities like press feedback on buttons and toast entrances with exact durations. The team gets a focused list instead of a wishlist, saving implementation effort and keeping the UI crisp.
A frontend lead wants to make a consumer app onboarding feel alive. They use the skill to hunt rare, high-emotion moments. It finds empty-state and success screens lacking delight, suggests bounce and stagger within budget, and explicitly rejects decorating functional lists. The output guides another agent via improve-animations to implement, raising perceived polish without harming usability.
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
