Agents place real design-system instances — tokens, components, variants — so every screen stays consistent by construction.
Consistency by construction
Most teams keep their design system consistent by remembering to check — eyeballing spacing, colors, and components in review. That breaks down the moment work moves fast or an agent is generating screens.
M2 makes the design system the thing agents build with, not a guideline they’re asked to follow. Every screen stays consistent because the system enforces it — not because someone remembered to.
Agents build with real DS instances
When an agent adds to the canvas, it places real design-system instances:
- Tokens — your colors, type, spacing, and radii, applied from the source.
- Components — the actual components from your library, not look-alikes.
- Variants — the right state and configuration of each component.
Because these are instances of your system, updates to the system flow through, and nothing drifts into a one-off.
Why it matters
- No drift. Screens can’t quietly diverge from the system.
- Faster review. You’re checking intent, not hunting for inconsistent spacing.
- Agents stay on-brand. They’re constrained to your system by construction.
Next steps
- Connect your AI agent over MCP and let it build on your design system.