The W3C Design Tokens Community Group is defining a JSON standard for design token interoperability — how tokens move between tools like Figma, Style Dictionary, and code. designtoken.md is the superset: a machine-readable markdown standard that gives agents rich design context, and its generator outputs DTCG-compliant JSON as one of its formats. It doesn't compete with DTCG — it includes it.
The W3C Design Tokens Community Group format is a JSON specification for design tokens. It defines how tokens should be structured so tools can interoperate: Figma exports in DTCG format, Style Dictionary reads it, your build pipeline transforms it. The spec covers types (color, dimension, font family, etc.), groups, aliases, and metadata. It's the emerging standard for design token exchange between tools.
JSON specA designtoken.md is the machine-readable standard for design context. The markdown gives agents full color scales, typography hierarchies, component states, and spacing systems in a format they read natively. But the generator also outputs DTCG-compliant JSON, CSS variables, and Tailwind config — so you get the DTCG format as one of many outputs, plus the richer markdown layer that DTCG can't express.
Markdown + DTCG JSON outputsDTCG standardizes token exchange for tools. designtoken.md provides the design context agents need at generation time.
A detailed comparison of what each standard covers.
| Feature | W3C DTCG | designtoken.md |
|---|---|---|
| Format | JSON | Structured Markdown + DTCG JSON, CSS, Tailwind outputs |
| Purpose | Tool interoperability | Agent context at generation time |
| Audience | Design tool makers, build pipelines | Developers using coding agents |
| Token structure | Flat/nested key-value with $type | Scales, hierarchies, semantic groups |
| Color representation | Single values | Full 50–900 scales with semantic roles |
| Typography | Individual properties | Complete hierarchies (9+ levels) |
| Component tokens | Not in scope | Button, card, input states |
| Relationships | Aliases ($value references) | Implicit via structure and naming |
| Requires tooling | JSON parser, build pipeline | Nothing — agent reads markdown |
| Spec status | Editor's Draft (ongoing) | Shipped, free, used in production |
Both standards serve different purposes. Here's how they fit together.
The generator already outputs DTCG-compliant JSON alongside the markdown. You get the interoperability format tools expect, plus the richer machine-readable layer agents need — full scales, hierarchies, and component relationships that DTCG's flat structure can't express. One generator, every format.