Design System Motion States

Summary

Created token-driven motion behaviors for components, improving consistency across product surfaces and interaction states.

Context

Multiple squads shipped UI with divergent animation habits. The system needed shared physics, timing, and intent so features felt like one product family.

Focus areas

• Component-level motion recipes (enter, exit, emphasis, error)
• Documentation for engineers and designers with live examples
• Alignment with brand voice: calm, precise, non-playful by default
• Lint-friendly naming for tokens reused across breakpoints

Outcomes

Less one-off tween work in delivery and perceptibly tighter cohesion across shells.