From Figma tokens to a React component library by Carolina FernandesFrom Figma tokens to a React component library by Carolina Fernandes

From Figma tokens to a React component library

Portfolio project
Carolina Fernandes
The problem For our bootcamp, I recreated Wise's web app as a real-world example of a design system done well. Design systems often live twice, once in Figma and once in code, and the two slowly drift apart. Colours get hard-coded, dark mode gets bolted on, and nobody's sure which version is right.
What I built
Primitive colour tokens in Figma (greys and creams) lined up one to one with Tailwind, so both sides use the same names.
Semantic tokens on top of them, like surface, card, text and action-primary, that point at the primitives instead of raw hex values.
The same tokens as CSS variables, with a light and a dark mode.
React components, including a customised shadcn Button with primary, secondary and tertiary variants, plus the cards from Wise's balance dashboard.
The full Git workflow, with commits, pull requests and merges.
How I designed it I started in Figma and named everything as if a developer would read it, because one would. Each component only uses semantic tokens, so switching to dark mode is a token swap, not a redesign. Then I built it in Cursor and Claude Code and checked every state against the Figma file.
The result One source of truth: change a token and both the design and the product update, in light and dark. The repo is private because it's taught in the paid bootcamp I co-teach at Memorisely, but I'm happy to walk you through it on a call. This is a learning rebuild of Wise's UI, not client work for Wise.

1 like · 7 views · Sep 22, 2026

I rebuilt Wise's dashboard as a token-based design system in Figma and React, so design and code stay in sync in light and dark mode.

Tags