Cross-platform Outputs
Static artifacts generated by `facet build` and one-directional export targets.
facet build emits multiple artifacts from one graph.
Build output set
tokens.css(rgboroklchvia--format)tokens.oklch.cssutilities.cssdemo.htmlplayground.htmltokens.dtcg.jsontokens.styledict.jsontokens.props.csstokens.lightdark.cssfacet.d.tstailwind.cssnative/tokens.rn.jsnative/tokens.jsnative/FacetTokens.swiftnative/FacetTokens.kt
One-dir quick notes
--format rgb|oklchcontrolstokens.cssemission.--minifywrites minifiedtokens.cssandutilities.cssin-place after emitting readable files.--outcustomizes output directory.
tokens.css vs tokens.oklch.css
Both contain layered CSS variable output. tokens.oklch.css uses full oklch values for native
Facet consumption; tokens.css uses compatibility rgb(var(--token)) style values where possible.
Interop exports (export not round-tripped)
facet tailwind <resolver> [--out file]→ Tailwind v4@themepresetfacet styledict <resolver> [--out file]→ Style Dictionary v4 JSONfacet export [--out file]→ pure DTCG export for default modefacet export --figma→ Figma Variables payload
facet export --figma is documented as one collection per axis and a primitives collection for
static tokens.
Figma payload constraints
From source export notes:
- only
COLORandFLOATvalues are written - float dimensions are emitted in px (unit metadata can be lost)
- cross-axis combinations are not represented as one combined Figma mode
- non-supported composite types require downstream style mapping
Cross-platform notes
Native emitter outputs are token-only maps:
- React Native:
native/tokens.rn.jswith all permutations - Swift:
native/FacetTokens.swift - Kotlin:
native/FacetTokens.kt
Planned status markers
These exporters are one-way in source docs; Facet remains the source of truth.