Learn how to go from Claude Code to Figma and back again Livestream with Anthropic: March 31, 9:00AM PST | 12:00PM EST

Join @brettmcm and @trq212 →

I'm not sure the workflow most people want is "code to Figma." Getting designs out of Figma into clean code is still the unsolved direction that actually costs devs hours every week.

Ah So designers need to understand code now AND developers are designing? Nobody is safe and I love it. 😂🔥

Wait.. isn’t Figma dying as a modern tool?

This is huge. Claude Code and Figma together is a game changer for design workflows. Definitely watching!

curious to see this in action. still figuring out how AI code truly integrates into design workflows.

Designers learning to code + devs turning into pixel-perfect designers = the end of job descriptions as we know them.😭

Figma is just a middleman as far as I can see. Designers could just build the components without adding them to Figma.

We need Figma to code, not other way around

This update might just give me more time to go outside and touch some grass, while clause builds my b2b healthtech decentralized opensource saas even quicker

@greenupek

Built by non-designers for non-designers lol

Figma just became a developer tool. With the new use_figma MCP integration, the gap between my IDE and my design canvas has officially vanished. Why this matters for builders: Cursor + Figma: I can now prompt a new UI component into existence using my team’s existing variables and rules. No more "Guesswork": The AI understands accessibility, spacing, and system constraints natively. Speed: We’re moving from "designing for a week" to "shipping in a day."

Can you send me a google invite

@grok new tools and features being added frequently, as of today what is the difference between Figma, Canvas, Nano Banana, Seedance, Sora etc.. and what is the best stack to use in Claude or any other CLI from the terminal?

@grok remind of this one hour before the time. My timezone is WAT.

This kills the context-switch tax forever. Finally building end-to-end without copying Figma links into Claude

claudes gonna figma me into oblivion lmao

@grok remind me of this meeting one hour before it commences

this loop is the actual unlock. generating code was never the only problem, losing taste every time you crossed the design/dev boundary was. going back and forth cleanly is cool

The design-to-code gap has been the biggest bottleneck in shipping for years. If this actually works well both directions it changes the solo dev workflow completely.

Reducing the handoff between implementation and design can shorten iteration dramatically. The real gain is keeping context intact while moving between thinking visually and changing the actual product.

Figma so expensive

The Claude Code + Figma workflow is going to be huge. Bridging the gap between design and implementation has always been the hardest part.

Brilliant! 💡

The interesting part is when AI works on real editable assets rather than generating something outside the workflow.

Always excited to learn from Thariq. Booked!

Awesome. I'm seated.

Icon states are a good example of why design-system context matters. "Off" often needs its own geometry, not just an overlay.

awesome

Ha ha ha ha, nice try ~ @stitchbygoogle

Finally, a real bidirectional loop between code and design! This is going to change how solo devs and small teams ship. Count me in for the March 31st stream.

Claude Code to Figma and back is the kind of integration that actually matters for design-development workflows. Reducing friction between tools is where real productivity gains happen.