Atlassian: the design system as structured content for AI
The design-system lesson
Craft guidanceDesign systems used to have two readers: designers and developers. AI agents are a third, and they cannot skim a Figma file or watch a video. Guidance that is not written down in a structured form gets replaced with something generic. Atlassian's line: documentation that drifts from the code is worse than none.
What they say they did (6 points)
- Atlassian found its design-system guidance spread across documentation sites, Confluence, Figma files, videos and code, some of it outdated and most of it written for people to look at.
- It broke the guidance into consistent, machine-readable chunks with schemas for components, icons, tokens, lint rules and foundations, kept alongside the code.
- Each schema covers usage, code examples, props, content standards and accessibility requirements.
- The same source generates its MCP server, its agent skill and its DESIGN.md files.
- Atlassian reports that agents using it produced 4.9% more accurate code with 11% fewer errors and finished tasks 34% faster than agents without it.
- It says unstructured sources led to outdated patterns, missed accessibility requirements and invented components.
Official source
- AtlassianAtlassian, Teaching AI to speak our design language(opens in a new tab)
- Authority
- Design-system convention
- Published
- 2 Jun 2026
- Last verified
- Verified 8 Oct 2026