Motion Foundation
Build an AI-ready Motion Foundation without starting from scratch
Turn inconsistent animations into usable motion logic your team can customize, document, and hand off to development
Trusted by Designers from
Motion gets messy when animations lack shared purpose. Most teams lack shared rules for timing, feedback, and reduced motion
_
Most motion systems stop before they become usable infrastructure
Having animations is not the same as having duration tokens, easing rules, reduced-motion behavior, and handoff logic
of teams connect tokens across design tools, code, and documentation
Source: zeroheight, 2026
+
of developers and designers say handoff between design and code could be improved
Source: Figma, 2025
1
Local animations
Motion decisions made locally without shared motion rules
2
Shared values
Reusable animations grouped by visual effect or interaction pattern
3
Primitive tokens
Durations and easing curves organized into a structured token model
4
Semantic roles
Motion tokens mapped to feedback, transitions, and system behavior
5
Documented rules
Rules explain purpose, duration, easing, reduced motion, and edge cases
6
System layer
AI context, handoff, accessibility, and teams share one motion model
Bring structure to your motion system, wherever you're starting from
Start from scratch, clean up existing animations, prepare handoff, or customize your motion logic with AI
Start with purpose, not just animation
Turn duration, easing, and transitions into reusable rules for feedback and speed
Turn animation values into a system
Audit motion patterns, fix inconsistent timing, and define shared motion behavior
Use AI without breaking motion logic
Adapt motion tokens with AI while preserving accessibility and implementation meaning
Bridge between design and code
Connect motion roles to tokens, reduced motion, and implementation guidance
From inconsistent animations to usable motion logic
Turn disconnected animation values into a structured system for timing, easing, feedback, reduced motion, and dev handoff
Inconsistent animation timing
Defined duration tokens with clear usage logic
Random easing choices
Easing rules tied to motion purpose
Developers guess animation values
Developer-readable motion handoff
Motion used as decoration
Motion tied to feedback, orientation, and usability
Reduced-motion behavior missing
Reduced-motion guidance built in
Transitions handled differently across product flows
Motion tokens mapped to implementation rules
Turn visual animation choices into reusable motion roles
Replace disconnected animations with semantic roles for feedback, transitions, loading, reduced motion, and handoff
Before
Local animations, mixed timing, unclear purpose, and repeated decisions
After
Duration tokens, easing rules, reduced-motion behavior, and developer handoff
Customize, document, and hand off your motion foundation
Adapt motion roles, document timing rules, and give devs logic for duration, easing, transitions, and reduced-motion behavior
Figma file
fig
Build from a structured motion foundation with duration tokens, easing tokens, semantic motion roles, and documentation in one file
Setup guide
Customize your timing scale, easing rules, feedback patterns, and reduced-motion behavior step by step without breaking the system structure
AI prompts
Audit motion usage, adapt timing roles, review accessibility risks, and prepare handoff with repeatable prompts
AI context
MD
Give an LLM the motion rules and constraints for safer customization
NotebookLM source
MD
Explore the system and generate briefings from one source
Accessibility
MD
Review reduced motion, distracting movement, flash risk, and animation risks
Dev handoff
MD
Explain motion roles, token mapping, reduced-motion behavior, and implementation
Make motion decisions easier for devs to implement consistently
The dev handoff file explains duration, easing, transition rules, and reduced-motion behavior before implementation
Token meaning
Explain what motion tokens represent and how to use them in design and code
Timing logic
Clarify duration, easing, feedback, transition, loading, and attention relationships
Usage rules
Show where motion roles should and should not be used to avoid local exceptions
Implementation notes
Give developers the logic behind motion and implementation
Use AI with motion system context, not generic prompts
Give Claude or another LLM the rules, constraints, and motion logic it needs to help without inventing a new system
OpenAI frames context optimization as a core lever for improving LLM accuracy
Source: OpenAI, LLM Accuracy Guide
Role-safe changes
Adapt duration, easing, feedback, transitions, and naming without breaking the model
System-aware audit
Find inconsistent timing, unclear purpose, duplicate animations, and weak transitions
Accessibility review
Check reduced-motion behavior, distracting movement, flash risk, and long-running motion
Handoff-ready notes
Turn motion logic into clearer implementation explanations for developers
Design Systems Surf has been really helpful in expanding my knowledge of design systems and best practices. The content is practical, well-structured, and easy to apply directly to my work
Piotr Wojtasiewicz
Developer
Use Motion Foundation when animation decisions get inconsistent
Whether you are starting from scratch, cleaning up existing motion values, defining feedback rules, or preparing developer handoff
Start from scratch with a motion system
When you are building a new product or design system, motion decisions can turn into disconnected animation values quickly. Motion Foundation gives you a structured model from day one: duration tokens, easing tokens, semantic motion roles, documentation, AI context, accessibility notes, and developer handoff
Outcome
You start with a motion foundation that is ready to customize instead of inventing every timing, easing, and transition rule from zero
Adapt existing animations into product roles
Audit messy timing and easing
Prepare handoff without guesswork
Deliver client-ready motion foundations
Built for teams and designers working on motion systems
Use Motion Foundation when timing, easing, feedback, transitions, and reduced-motion need structure, documentation, and handoff
01
Product designers
Turn product interactions into reusable motion roles for feedback, transitions, and flows
02
UI designers
Turn visual animation choices into rules for timing, easing, feedback, and usability
03
Freelancers and agencies
Deliver motion systems with documentation, accessibility, handoff, and AI context
04
Design system leads
Turn existing motion decisions into rules for timing, easing, feedback, and usability
Based on analysis of 100+ design systems. Patterns translated into a reusable motion foundation
Since 2023, Design Systems Surf has cataloged mature design systems across foundations, components, documentation, and implementation patterns.
Motion Foundation turns that research into reusable timing roles, easing rules, motion principles, AI context, accessibility guidance, and handoff.
Save 16–24 hours on motion system work and documentation
Motion Foundation removes repetitive setup, documentation, AI context, accessibility, and handoff work
Trusted by designers working on design systems
Feedback from people building, auditing, documenting, and maintaining design systems
10k+
Designers across 175+ countries follow Design Systems Surf for design system examples, patterns, and practical resources
What to know before you start
Clear answers about what Motion Foundation includes, how it can be customized, and how it fits into real design system work
Is this just a Figma template?
No. The Figma file is one part of the package. Motion Foundation also includes AI context .md, NotebookLM source .md, setup guidance, AI prompts, accessibility .md, and dev handoff .md.
The Figma file gives you the working motion system. The Markdown files support different AI workflows: customization, knowledge exploration, accessibility review, and developer handoff.
What is included?
Can I customize it?
Will this fit my brand?
Can I use it with an existing design system?
Do I need to use AI?
Are the Markdown files standalone guides?
What does the NotebookLM source do?
What does the accessibility file do?
What does the dev handoff file do?
Does this include components?
Does this include animation presets?
Does this support reduced motion?
Who is this for?
Is this for beginners or advanced teams?
How is this different from building it myself?
Will developers be able to use it?
Can I use this for client work?
What is not included?
Still have questions?
Reach out at hey@designsystems.surf
