This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Stop hand-copying design tokens into Figma. Turns your DESIGN.md tokens into a working Figma system: a typed Variable Collection (colors/spacing/radius), Color Styles bound to those variables, Text Styles per typography entry, and a labeled documentation frame — all generated automatically. Built for re-runs: update DESIGN.md and regenerate — tokens update in place, removed ones get cleaned up, docs frame replaces itself (no duplicates). Doesn't build Components or Effect Styles yet.
I'm Dana, a Product Designer building the design system at Farmacare. Excited to launch DESIGN.md → Figma today!
The problem: every design system starts with a spec — colors, type scale, spacing, radius — usually written down in a DESIGN.md or similar. But getting those tokens into Figma as real Variables and Styles is manual, tedious, and drifts out of sync the moment the spec changes.
This plugin closes that gap. Point it at your DESIGN.md, and it generates a properly typed Variable Collection, Color Styles bound to those variables, Text Styles per typography entry, and a labeled documentation frame — all in your Figma file. Update the spec and re-run it: matching tokens update in place, removed ones get cleaned up, no duplicate docs piling up.
It doesn't build full Components or Effect Styles (yet) — those need more than token data to do properly — but for keeping your foundational tokens honest, this has saved my team hours every time our design system evolves.
Would love your feedback, especially if you're running your own design system workflow.
No comment highlights available yet. Please check back later!
About DESIGN.md to Figma on Product Hunt
“Your DESIGN.md, synced straight into Figma”
DESIGN.md to Figma was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #145 on the daily leaderboard. Stop hand-copying design tokens into Figma. Turns your DESIGN.md tokens into a working Figma system: a typed Variable Collection (colors/spacing/radius), Color Styles bound to those variables, Text Styles per typography entry, and a labeled documentation frame — all generated automatically. Built for re-runs: update DESIGN.md and regenerate — tokens update in place, removed ones get cleaned up, docs frame replaces itself (no duplicates). Doesn't build Components or Effect Styles yet.
DESIGN.md to Figma was featured in Design Tools (262.2k followers) and User Experience (367.9k followers) on Product Hunt. Together, these topics include over 76k products, making this a competitive space to launch in.
Who hunted DESIGN.md to Figma?
DESIGN.md to Figma was hunted by I Putu Dana Putra. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how DESIGN.md to Figma stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
I Putu Dana Putra
👋 Hey Product Hunt!
I'm Dana, a Product Designer building the design system at Farmacare. Excited to launch DESIGN.md → Figma today!
The problem: every design system starts with a spec — colors, type scale, spacing, radius — usually written down in a DESIGN.md or similar. But getting those tokens into Figma as real Variables and Styles is manual, tedious, and drifts out of sync the moment the spec changes.
This plugin closes that gap. Point it at your DESIGN.md, and it generates a properly typed Variable Collection, Color Styles bound to those variables, Text Styles per typography entry, and a labeled documentation frame — all in your Figma file. Update the spec and re-run it: matching tokens update in place, removed ones get cleaned up, no duplicate docs piling up.
It doesn't build full Components or Effect Styles (yet) — those need more than token data to do properly — but for keeping your foundational tokens honest, this has saved my team hours every time our design system evolves.
Would love your feedback, especially if you're running your own design system workflow.
Thank you!