Design tokens now travel with motion, not just colour
Published 10 September 2026 · Source dated 5 September 2026
Figma's new Motion tool exports through its MCP server, extending the design-token pattern (already standard for colour, spacing, type) to animation timing and easing.
Buried in the Figma Motion launch: exports don't just spit out CSS values, they stay connected through Figma's MCP server, so a coding agent gets live animation specs rather than a screenshot to guess from. That's the same pattern design systems already use for colour, spacing and type tokens — Figma is just extending it to motion.
For anyone maintaining or contributing to a design system, this is worth watching: if animation timing and easing become tokens too, "redlines for motion" stops being a manual, ambiguous handoff step between design and dev.
It's early — most teams don't have motion tokens formalised yet — so this is a "watch it, don't rebuild your system around it yet" moment.
Coach
Open your team's (or a personal) design system file and note whether motion/easing values are documented anywhere — if not, flag it as a gap worth raising.
Google's Material Design 3 popularised dynamic, token-based theming back in 2021, and it's still what most design-system setups get measured against. If you're building variables in Figma or tokens in Penpot, M3's structure is worth studying, not because it's new, but because it's proven.
open Material 3's token docs and compare their primitive-vs-role token split against your own Figma or Penpot library — note one gap you could fix this week.
Creative Market's 2026 trend forecast flags 'Glasscore' — blur, glow and translucent layers — as a rising visual style. For teams running token-based design systems, that means more theming flexibility, not just flat colour tokens.
Open your team's (or a starter) design system file and check whether blur/elevation tokens exist — if not, sketch one variant using Figma or Penpot's effect styles.
Some teams are wiring AI coding assistants into their design token workflow, using rules and MCP connections to keep components consistent. It's promising but still fragile in practice.
pick one component in your (or a practice) design system and check whether its tokens are named consistently enough that an AI tool could use them without guessing.
