All notes
Process · 5 min read

Designing with Claude Code and Figma MCP

How a designer ships a front end without waiting for a sprint.

For most of my career, a design ended at a handoff. I'd share the Figma file, walk engineering through it, and then wait to see what came back. Something always got lost on the way: a spacing rule, an empty state, the way a table should behave on a phone.

These days I take my own designs to working software. Not instead of engineers, but so the first thing a team reviews is something they can click.

The loop

  1. Design in Figma. Same as always: system first, then flows, then screens.
  2. Read the design with Figma MCP. Claude Code reads the real file (frames, variables, components) instead of guessing from a screenshot. What gets built starts from the design's actual values.
  3. Build with Claude Code. HTML and CSS, or React and Next.js. I read every diff the way I'd run a design review: is the hierarchy right, does it hold up with real content, what happens at 390px?
  4. Push to Git, review on Vercel. Every branch gets its own preview link, so feedback happens on a live page, on the reviewer's own phone, not on a PDF.

What it changed on this site

This website is the clearest example. It's static HTML and CSS with a small build script, deployed on Vercel. Every change goes through a branch, a pull request and a preview link.

  • Case-study images come from the real files. Instead of screenshots, the screens are exported from the original Figma projects as vectors, then cleaned up by a script. One work card went from a 536 KB vector to a 44 KB image with no visible difference.
  • The homepage redesign started as code. I built three visual directions as live pages instead of three mockups, then picked one by using them on a laptop and a phone. You notice different things when the type is real and the page scrolls.
The point isn't that AI writes the code. It's that the gap between "designed" and "real" shrinks to a link.

What I still do by hand

Judgement doesn't move to the tool. Deciding what to cut, how a page should read in 30 seconds, whether a label makes sense to someone new: that's still the job. So are the checks that stop a fast build from being a sloppy one: contrast, focus states, tap targets, image weight, and looking at every screen before it ships.

Why it matters to a team

  • Engineers get a working reference, not a redline document to decode.
  • Edge cases show up earlier, because real content and real screen widths are there from day one.
  • Reviews get faster, because everyone reacts to the same live link.

It's how I'd like to work on any product team: design it, build the first version, then hand over something that already works.

Need a designer
who ships?

info@hellosaiful.com Book a 30-min call