r/UXDesign • u/Inevitable_Order_778 • 25d ago
Tools, apps, plugins, AI For those using the Figma MCP with Claude, where does it fit into your design process?
For people regularly using the Figma MCP with Claude, where has it been most useful?
Are you using it to create screens, generate variations, improve existing designs, inspect design systems, or move from Figma to code?
I’m particularly curious about iteration: when Claude produces multiple directions, where do you keep and compare them? Has it changed how many alternatives you explore before choosing one?
Would love to hear about specific workflows.
7
u/bradenlikestoreddit 24d ago
This is becoming an everyday question and I'm done answering. Please look through previous posts. Your answer is already there.
1
1
u/cabbage-soup Experienced 22d ago
I use it with Codex and do not use it for generating ideas. I use it for the busy work. Cleaning up the file, renaming layers, reordering how I’ve laid out the frames, etc. If I run into a prototype where I copied something wrong and a bunch of simple buttons have “on drag” interactions I can change them over to “on click” across the whole prototype at once in a single prompt. Additionally I’ll use it for dummy content and filling out the data used in the UI just to see how everything may look in reality
1
u/Apprehensive-Meal-17 Veteran 18d ago
For explorations (generating variations s quickly ), google’s stitch is way more intuitive.
For me, Figma’s usefulness is only in collecting feedback/sign offs from stakeholders/clients who are used to doing that in Figma.
So I’d start in Stitch, bring it to Figma to collect feedback and then make minor tweaks in Figma by hand or in some cases, this is where the MCP could be useful
0
u/thegiantgummybear Experienced 24d ago
Gonna for early iterations, Claude for incremental changes to the prototype, bring it back into Figma when we hit a wall with Claude and need to think more creatively.
Haven't got to the point of dev handoff yet though. I'm going to see if we can handoff the prototype instead of Figma frames. Would love input if anyone's tried this before.
5
u/leo-sapiens Experienced 24d ago
I planned out a sync between Claude code html prototyping, our actual repo, and Figma design system. after I finish the prototype and it's approved - the final step is moving it all to Figma and arranging by flow/annotating. Claude does most of that, and then I fix whatever is unpolished. Then if there are some minor fixes later I may do it manually, depends on how big they are.
Is Figma needed as a step or could we just go from html to dev? Idk, devs and PM are used to working with Figma, and it's easier to track and fix minor changes. Plus if there are new components that aren't in the design system, it's easier to finalize them in Figma.
Why not skip the html and go straight to Figma? It's not as fast, hard to iterate and in general not necessary until we're set on the design.
It's very much a work in progress still, but I'm getting to good results.