Interaction & Motion Library treats interface behavior as a system. Instead of animating screens one at a time, I capture state, feedback, transitions, and rhythm as reusable motion primitives, so the way a product moves stays consistent from brand guidelines down to code.
What's in it
- Motion tokens: durations, easings, and distances defined once and shared, the same way color and type tokens are.
- Transitions: named, reusable patterns for how elements enter, change, and leave.
- Rhythm: the timing and stagger rules that make a set of transitions feel like one system rather than a pile of one-off animations.
This is the layer that keeps interface motion coherent as a product grows and more people touch it. It is an ongoing system, refined across projects rather than shipped once and left alone.