Figma to React handoff checklist for design engineers
A Figma to React handoff checklist: tokens and variables, variants mapped to props, every UI state, responsive rules, motion, accessibility and Code Connect.
Most handoff problems are not code problems. The screen looks finished in Figma, the React version looks finished in the browser, and the two disagree about what happens when the name is 60 characters long, the request fails, or someone tabs through the form.
I take interfaces from Figma to production React at MedRoyale, where building a design system cut our design-to-dev handoff time by about 80%. A design system only pays off if each screen arrives with its questions already answered, so this is the checklist I run on a screen before it becomes components. Run it with the designer, not at them.
Tokens and variables
- Every colour, radius, spacing and type value is a variable or style, not a raw hex. A raw
#3B6CF6in a frame becomes a raw value in code, and then the two drift. If a value has no token, decide now whether it needs one or is a mistake. - Variable names match the names in code. If the code uses
--color-inkor a Tailwindtext-inkclass, the Figma variable should becolor/ink, notText Primary Dark. Set the variable’s code syntax for Web so Dev Mode shows the real name when you inspect. - Themes are modes, not duplicate frames. Light and dark should be two modes of the same variable collection. Then you check one frame in both modes instead of comparing two frames by eye.
- Spacing comes from a scale. A gap of 13 px is almost always a nudge, not a decision. Snap it to the scale or write down why it is different.
Components, variants and props
- Each Figma component maps to one React component. If the designer has
Button,Button SmallandButton Iconas separate components, agree on whether code has oneButtonwith props or three components. - Variant properties read like props.
size=sm|md|lg,variant=primary|secondary|ghost,disabled=true|false. If a property cannot be named as a prop, it is probably two components hiding in one. - Boolean and instance-swap properties are listed. “Has icon”, “show badge”, and the swappable icon slot all become props or children. Missing them is how a component ends up with six near-copies.
- Detached instances are found and explained. A detached button is either a one-off that should not exist or a new variant nobody added to the library.
- Check against the library you already have. If the code side uses something like shadcn/ui, map Figma components to its parts before building anything new.
States
- Interactive elements have hover, focus-visible, active and disabled. Focus is the one most often missing, and the one keyboard users rely on.
- Async screens have loading, empty and error states. A table needs a first-load skeleton or spinner, a “no results” state, an “error, try again” state, and what a partial failure looks like.
- Forms have validation states and messages. Where does the error text go, what does it say, and when does it appear: on blur, on submit, or while typing?
- Success is designed too. What the user sees after saving, sending or deleting is part of the screen.
Responsive rules
- Frames exist for the breakpoints the code uses. At minimum mobile and desktop, with the breakpoint values written down, not implied by frame widths.
- Auto layout says what stretches. Fill container versus hug contents is the difference between a card that grows and one that leaves a gap. Fixed widths in a frame should be deliberate.
- Behaviour between breakpoints is described. What wraps, what collapses into a menu, what scrolls horizontally, what disappears. Two static frames do not show this.
- Tables and dashboards have a narrow-screen plan. Horizontal scroll, stacked cards, or hidden columns. Decide before the data arrives.
Content edge cases
- Long text is tested. Long names, long titles, long numbers, and the longest translated label. Translated strings can run much longer than the English, so a bilingual product needs both tested.
- Truncation rules are explicit. Ellipsis after one line, clamp at three lines, or wrap freely. Say which, and whether a tooltip shows the full value.
- Real data shapes are used. Zero items, one item, a hundred items, missing avatars, null values. Lorem ipsum hides every one of these.
- Numbers, dates and currency have a format. Decimal separators, time zones and currency symbols are design decisions.
Motion
- Each animation has a trigger, property, duration and easing. “Fades in” is not a spec. “On enter, opacity 0 to 1 and y 8 px to 0, 0.4 s, ease-out” is.
- Reduced motion is specified. What happens when
prefers-reduced-motionis set: no animation, or a simple fade? - Prototype links match the spec. If the prototype uses smart animate, write down what it is meant to show, because code will not copy a prototype exactly.
Accessibility
- Contrast passes WCAG AA. At least 4.5:1 for normal text and 3:1 for large text and for UI parts like borders and icons, per the WCAG contrast guidance. Check both themes.
- Focus order is written down for complex screens. Dialogs, menus and multi-column forms are where the visual order and the DOM order part ways.
- Every input has a visible label, and icon buttons have an accessible name. A placeholder is not a label. A trash icon needs “Delete row” somewhere, even if only in an annotation.
- Tap targets are big enough. WCAG 2.2 asks for at least 24 by 24 CSS pixels, with a few exceptions. I aim higher on touch screens.
Assets
- Icons come from one set, as components. Not flattened vectors pasted from three libraries.
- Images have export settings and a role. Format, sizes for each breakpoint, and whether each image is decorative or needs alt text.
- Illustrations are exportable as SVG where possible, with stray hidden layers and masks cleaned up first.
Dev Mode, Code Connect and the MCP server
- The frame is marked ready for dev. Dev Mode statuses tell developers what is final, and compare changes shows what moved since they last looked.
- Annotations carry what the canvas cannot. Behaviour, accessibility notes and measurements that matter go in Dev Mode annotations, not in a separate document that goes stale.
- Components are linked with Code Connect. Code Connect maps Figma components to your real components, through the in-app UI or the CLI in your repo. Dev Mode then shows a snippet of your actual component next to the generated CSS. At the time of writing (November 2026) it needs a Full or Dev seat on a paid plan.
- AI tools get design context, not screenshots. If you generate code with an agent, connect the Figma MCP server. Code Connect mappings flow into it, so the agent reaches for your components instead of inventing new ones.
Naming
- Layers are named for what they are.
Frame 427tells nobody anything. Name the layers that become components or landmarks. - Pages and frames follow one convention. Feature, then screen, then state, for example
Billing / Invoices / Empty. - Component and prop names are the same on both sides. If Figma says
Chipand code saysTag, someone will build both.
How to use this list
Do not hand it to a designer as a gate. Walk through it together on the first screen of a feature, fix what is missing in Figma, and the next screens get faster because the gaps are already closed. In my experience that habit matters more than any plugin.
If you are wondering whether this work belongs to a designer or a developer, I wrote about that in design engineer vs frontend developer. And when the site itself is ready to ship, the launch checklist takes over.