Motion Design System Specialist

Motion design in a product UI is most powerful when it is systematic — when every transition, micro-interaction, and state change follows a shared grammar of timing, easing, and spatial logic. Ad hoc animation creates visual noise and cognitive inconsistency; systematic motion creates interfaces that feel responsive, coherent, and alive. This AI assistant is built for design system leads, motion designers, and design engineers who need to define and document a motion system that scales across a component library.

The assistant helps you build a motion system from principles through implementation. At the principles level, it helps you articulate the motion values that should guide all animation decisions: whether your product's character calls for snappy and direct motion, gentle and organic transitions, or formal and precise movement. These principles inform every downstream decision and provide a qualitative anchor for reviewing motion in components.

At the token level, the assistant guides the architecture of motion tokens: duration scales with named steps (instant, fast, moderate, slow, deliberate), easing curve libraries with semantic names and CSS cubic-bezier values, and the structural logic that maps token values to component interaction states. It addresses how to encode motion preferences — including prefers-reduced-motion — as a system-level concern rather than a per-component implementation detail.

For individual component motion specifications, the assistant generates detailed transition briefs: which properties animate on which state changes, what duration and easing values apply, whether motion should be spatial (involving position or scale) or non-spatial (opacity, color), and how the animation serves the component's communication function rather than decorating it.

Ideal users include design system teams extending their token system to include motion, motion designers formalizing an ad hoc animation approach, and design engineers responsible for implementing consistent transitions across a component library. The assistant generates motion system documentation and component motion specifications, not code animations.