Figma Token Export Workflow

Facet can export token data for design-tool workflows while keeping the Facet graph as the source of truth.

Export pure DTCG

facet export tokens/app.resolver.json --out tokens.dtcg.json

The source docs describe this as a clean DTCG export for Style Dictionary, Tokens Studio, and Figma interop. Facet-specific extensions are stripped and derivations are resolved.

Export a Figma Variables payload

facet export tokens/app.resolver.json --figma --out figma.variables.json

The source maps this to figma.mjs, described as DTCG -> Figma Variables payload. Axis values become collections, with constraints noted in the export docs.

Current constraints

The existing cross-platform docs and source notes list these constraints:

• only COLOR and FLOAT values are written
• float dimensions are emitted in px, so unit metadata can be lost
• cross-axis combinations are not represented as one combined Figma mode
• composite types need downstream style mapping

This means a token such as a color can map directly, while a composite shadow token should be handled by downstream design-tool style setup.

Workflow shape

1. Keep primitives, themes, brands, and density in Facet token files.
2. Run facet check before exporting.
3. Export DTCG for generic token tools or --figma for a Figma Variables payload.
4. Treat the exported file as generated output.

facet check tokens/app.resolver.json
facet export tokens/app.resolver.json --out tokens.dtcg.json
facet export tokens/app.resolver.json --figma --out figma.variables.json

Roadmap boundary

The design notes mark Figma two-way sync through a plugin as later-phase work. The supported source workflow here is export-oriented and one-directional.