motion-craft

# Motion Craft Animations that communicate, not decorate. Every frame must earn its place. Inspired by Emil Kowalski (Linear, Sonner, Vaul), Paul Lewis (Google Chrome), and the CSS Animation Working Group. ## Workflow ## The Animation Decision Framework Before writing any animation code, answer these four questions in order. ### 1. Should this animate at all? | Frequency | Decision | Reason | |-----------|----------|--------| | 100+ times/day (keyboard shortcuts, command palette, search toggle) | No animation. Ever. | Animation makes frequent actions feel delayed. Raycast has no open/close animation. Optimal. | | Tens of times/day (hover effects, list navigation) | Remove or drastically reduce | Users notice animation latency on repeated interactions | | Occasional (modals, drawers, toasts) | Standard animation | The right place for motion | | Rare / first-time (onboarding, confirmation, celebration) | Add delight | These moments earn longer, richer animations | **Never animate keyboard-initiated actions.** These repeat hundreds of times daily. ### 2. What is the purpose? Every animation must have a clear answer to "why does this animate?" | Purpose | Example | Valid? | |---------|---------|--------| | Spatial consistency | Toast enters and exits from the same direction | ? | | State indication | Button morphs to show "sent" | ? | | Feedback | Button scales down on press, confirming the interface heard the user | ? | | Preventing jarring changes | Elements fading i...