← All Resources
Canon
Figma Integration
Code remains the source of truth. Figma consumes exported token artifacts so design and implementation stay aligned without inventing a second canon.
Published April 14, 2026
Source Of Truth
Start from packages/canon/src/lib/styles/tokens.css. The additional artifacts exist to move that same token system into other tools.
Files To Use
packages/canon/src/lib/styles/tokens.figma.jsonfor Tokens Studio style importspackages/canon/src/lib/styles/tokens.dtcg.jsonfor standards-oriented token pipelines@create-something/canon/styles/tokens.figma.jsonand@create-something/canon/styles/tokens.dtcg.jsonfrom the packaged library surface
Recommended Workflow
- Change tokens in code first.
- Treat exported JSON files as derived artifacts, not hand-edited sources.
- Re-import the Figma-facing artifact when token values change.
Documentation Status
The long-form walkthrough for Tokens Studio and end-to-end sync is still being rewritten. This page is live now so the Canon resources section no longer points at a 404.