What is the interaction physics skill?
Interaction physics is a skill in the vibe-building-skills library by Sanket Dongre. It makes an AI coding agent inspect existing motion, write a project animation spec with duration and easing tokens, implement feedback in CSS or your motion library, and add reduced-motion support.
It is one of 13 frontend design skills in the vibe-building-skills repo. Its prime directive is that every animation must confirm an action, guide attention or explain a state change. Motion that does none of these gets deleted.
The skill delivers two things together: a written animation spec for the whole project, and the implemented transitions for the flows you named. The spec keeps future motion consistent after the audit is over.
What changes in your agent's output
- Scattered hover durations such as 150, 200, 250 and 300ms collapse into three or four named tokens like fast, base and slow.
- Entering elements ease out, exiting elements ease in, and exits run at roughly 75 percent of the enter time.
- Only transform and opacity are animated, with shadow motion faked by crossfading a pseudo-element.
- A prefers-reduced-motion block ships in the same change, and every hover effect gets a focus-visible twin.
- Modals, toasts and form errors that used to pop in get a transition.
Who the interaction physics skill is for
Best for
- Apps that feel janky, flat or inconsistent and need a single timing vocabulary.
- Teams who want an animation audit with fixes listed per file.
- Projects that already use a motion library, since the skill implements with what you have.
- Reviews that must cover reduced motion and flash rate.
Not for
- Choosing which loading indicator to show. The skill hands that to the loading-states skill and only animates the result.
- Layout thrashing or frame budget work, which it hands to design-engineer-mindset.
- Scroll-driven showpieces, since the hard rules forbid scroll-hijacking.
Where it fits next to other motion skills
If you want a lookup of easing and stagger rules, Animation Principles covers that ground. For a token-first view see Motion System, and for dropped frames see Animation Performance.
Use it with UiChemy
Interaction physics tunes motion in your front-end code. If you build with AI and need the result as an editable WordPress page, UiChemy AI to WordPress imports an AI build. Click Get Started on uichemy.com.
How to install Interaction Physics Skill: Motion Spec and Timing Rules
git clone https://github.com/sanky369/vibe-building-skills.gitThe README says each skill is a standalone SKILL.md, so you can install just this one without the other 39.Clone the repository
Run the clone command above. The README gives no package installer, so the skill lives as a folder in the repo at
skills/frontend-design/interaction-physics/.Add the skill to your agent
The README describes uploading the SKILL.md in Claude under Settings, Capabilities, Skills, then Add Skill. For a folder-based agent, copy the whole
interaction-physicsfolder, including its references folder, into your skills directory.Start from the orchestrator if unsure
The README suggests beginning with frontend-orchestrator, which assesses design maturity and sequences the 13 frontend skills. You can also call this one directly.
Describe the job
Say what is wrong, for example that the modal just pops in or the buttons feel dead. The skill audits first, states its assumptions, and asks only about personality and scope if they cannot be inferred.
Check that it loaded
Ask the agent to list its skills, or name the skill in your prompt. The description should match the trigger text in SKILL.md.
Key features
- Step 0 codebase inspectionThe agent greps for transition, animation, keyframes, framer-motion, react-spring, gsap and Tailwind transition classes, and records every duration and easing in use. Inconsistency is usually the first finding.
- Animation spec firstFour duration classes: micro feedback at 150 to 250ms, structural transitions at 300 to 500ms, attention at 500 to 1000ms, and continuous loops near 1s with linear easing.
- Easing by directionEntering elements decelerate, exiting elements accelerate, on-screen moves ease in and out, and only mechanical loops use linear. Bouncy curves are limited to one or two deliberate places.
- Four-part microinteraction anatomyEach interaction is written as trigger, rules, feedback, and loops and modes. State-driven transitions are preferred over keyframes when a user can toggle something rapidly.
- Compositor-only propertiesAnimate transform and opacity. Width, height, top, left and box-shadow are not animated directly, and background-color is allowed only for small controls.
- Reduced-motion baselineDecorative motion disappears while informational motion such as progress may stay as opacity only. A baseline block lives in references/patterns.md.
- Accessibility rulesFeedback never rides on motion alone, hover effects need focus-visible equivalents, and nothing flashes more than three times per second.
- Required spec outputThe reply includes motion tokens, an interaction inventory, audit findings and a list of what was deliberately not animated.
- Quality bar and hard don'tsA checklist covers purpose, tokens, easing, properties and reduced motion. Hard don'ts include scroll-hijacking, animating keystrokes in text inputs and adding a motion library when CSS is enough.
Frequently asked questions
What is the interaction physics skill?
It is a SKILL.md in sanky369/vibe-building-skills that covers the motion layer of a UI: microinteractions, transitions, hover and press feedback, and timing and easing. It produces an animation spec with tokens plus implemented CSS or JS, and audits existing motion for performance and reduced-motion support.
How do I install the interaction physics skill?
Clone the repository, then add skills/frontend-design/interaction-physics to your agent. The README describes uploading SKILL.md through Claude Settings, Capabilities, Skills. It gives no package installer, so for folder-based agents copy the whole folder, including references, into your skills directory.
What durations and easing does it recommend?
Micro feedback runs 150 to 250ms with ease-out, structural transitions 300 to 500ms, attention effects 500 to 1000ms with ease-in-out, and continuous loops about 1s with linear. Exits are shorter than entrances, roughly 75 percent of the enter duration.
Does it add an animation library to my project?
No. The skill says to implement with the motion library you already use, and otherwise default to CSS transitions and keyframes. One of its hard rules is never to add a motion library for effects that CSS can already do.
Does it handle prefers-reduced-motion?
Yes. The reduced-motion block is meant to ship in the same change as the animations. Decorative motion is removed, and progress-style motion may remain as opacity only. Every animated state change must also change color, text or an icon, so it still reads without movement.
Why only transform and opacity?
The skill treats them as compositor-friendly. It tells the agent not to animate width, height, top, left or box-shadow directly, and to fake a shadow animation by crossfading the opacity of a pseudo-element. Small controls may still animate background-color.
Does it work with Claude, Cursor or Codex?
The repo README covers installing skills in Claude and using Claude Code for implementation. It states nothing about Cursor or Codex, so check your agent's skill support. The skill is a plain SKILL.md folder with a references file, which other tools may be able to read.
Can this skill build a WordPress page?
No. It edits front-end CSS and JS in your project. To turn an AI-built page into an editable WordPress page, UiChemy AI to WordPress imports an existing AI build. Click Get Started on uichemy.com to begin.


