UI/UX Motion System

Purpose

Treat motion as a semantic layer between interface states, not decoration added because a library is available. Motion may communicate feedback, state change, hierarchy, continuity, orientation, progress, or spatial relationships. If it has no clear job, remove it.

Context discipline

Start with context-index.md, the current handoff, relevant flow and state contracts, and the specific screen or component under review. Load motion-spec.md and motion references only when motion is the active decision. Keep raw recordings, rejected explorations, and long timing experiments outside the active context.

Workflow