Roadmap
What is being worked on, and what is only an idea. Nothing here has a committed date.
How to read this page
Items are grouped by how firm they are, not by when they will ship. Two of the larger items exist as draft specifications only — they have been written up but not scheduled or started. They are listed because knowing they are planned changes how you would design around today’s gaps.
In progress: DTCG 2025.10 completion
The token layer is being migrated type by type to full DTCG 2025.10 compliance. Most of it is done — see feature status.
| Remaining | What it needs |
|---|---|
| Gradient | Everything: an input field, a display formatter, a spec-shaped validator (the current one still expects a CSS string), and an applicator |
| Stroke style object form | The input converter rejects { dashArray, lineCap }, so it can only arrive via import |
Queued fixes
These are the known limitations with the clearest path to a fix:
| Fix | Why it matters |
|---|---|
| Font weight apply mapping | Numeric weights and DTCG keywords should map to Figma style names, as the typography applicator already does |
| Font family array apply | A fallback stack should be walked, not joined into one string |
| rem → px in border width and dash arrays | Currently inconsistent with every other applicator |
| Reference check on delete | Deleting a token should warn about referrers instead of silently breaking them |
| GitLab and HTTP endpoint domains | Adding them to the network allowlist would make two implemented providers usable |
| Working undo / redo | The buttons exist and do nothing |
| Reachable reset and provider management | Both currently live behind an unmounted panel |
Specified but not started
Token Wizard Draft spec
A guided flow that generates a complete, validated token system instead of requiring you to author it token by token.
The draft describes a nine-step interview producing a three-tier
primitives / semantic / component structure across brand, mode, and density
axes, with contrast checking before anything is written and a defaults path
targeting under ten minutes to a first token set.
Why it matters for you today: the plugin currently has no bootstrapping. Every system starts from an empty document or a pasted JSON file.
MCP bridge Draft spec
A Model Context Protocol server letting an AI coding assistant read and write the live token document while the plugin is open, over a localhost WebSocket — no copy-pasting JSON between Figma and an editor.
The draft describes a new Connect tab with a connection status pill, and tools for reading, searching, and importing tokens.
Not planned
Being explicit so you do not wait for these:
| Why | |
|---|---|
| Reading existing Figma styles or variables into tokens | Import is JSON-only by design |
| Applying duration, cubic Bézier, or transition tokens to layers | Figma has no matching layer property |
| Composite tokens as Figma Variables | Figma variables have four scalar types; there is nothing to map to |
| Merge-conflict resolution in sync | Out of scope for the current sync model |
Influencing it
The queued fixes are ordered by how often they bite people. If one of them is blocking you, saying so moves it up. Include what you were trying to do, not just which bug you hit — the workaround is sometimes better than the fix.