The thing that makes a design token portable. A token is a name and a value with no
platform attached; Style Dictionary is the pipeline that turns that JSON into whatever
each platform reads — --color-primary for the web, a Swift constant, an XML resource —
so the decision is made once, upstream, and every implementation inherits it.
Here it runs in the Design Tokens Transformer: upload a token file, pick the output formats, and compare Style Dictionary's build against the hand-written transformers side by side. The lab detects three dialects — the DTCG standard, the older Style Dictionary shape, and Helium, the estate's own export from Figma — because the practical question is never whether tokens can be transformed but whether the tokens a team already has can be.
That is also why it sits under the platform-agnostic contracts: a token layer both an AEM component and an Edge Delivery block can be realized from is the first contract worth writing, and Style Dictionary is how it reaches either side.
