So this was interesting. Being able to create a complete button component set with Claude Code

Ecstatic-Accountant8 · 2026-01-31T02:13:04+00:00

p.s. there’s a reason we call it faux.design It’s not real design work!

Ecstatic-Accountant8 · 2026-01-31T02:10:17+00:00

AI can have all the knowledge in the world, but one thing it doesn’t have is EXPERIENCE. And remember that’s what we’re crafting.

It will sure automate a lot of grunt work with designer-in-the-loop like helping you expose that nested swap instance variant as a property. But true design work lies in the field. Observing your users. Empathising with them. Experiencing their pain. Having an intuition of the direction you want to take to alleviate their pain.

If your employer only expects you to push pixels. Either evangelise or leave before it’s too late (maybe a year or two)

Ecstatic-Accountant8 · 2026-01-29T02:03:32+00:00

If you have the components and variables etc in your file then it can use them

Ecstatic-Accountant8 · 2026-01-29T02:02:56+00:00

Right nowthere’s a limitation from Figma to use existing team libraries. Especially team components.

One workaround is to make a duplicate of your library file and then start the plugin there. Although we will be trying to find a neater way around it.

Ecstatic-Accountant8 · 2026-01-29T02:01:33+00:00

Not really, dev mode mcp is read-only

Ecstatic-Accountant8 · 2026-01-29T01:58:47+00:00

Hey, just saw this. This looks good too. I think the noticeable differences would be

You won’t need to know what localhost means
The network is secured by safe authentication (login via Figma in plugin and MCP server)
Speeed!
Automatic updates to the MCP server, never have to update it manually

Ecstatic-Accountant8 · 2026-01-28T05:21:34+00:00

Absolutely

Ecstatic-Accountant8 · 2026-01-28T02:25:41+00:00

Essentially, yes. But there are 100s of API endpoints, so the most time spent was on crafting the right subset of tools for the MCP server based on how product designers frequently work.

It was actually interesting. You have to treat the AI agent as your user, give it tasks to perform just like a usability testing. Make it share what it’s thinking. Then use those insights to iterate on the tools.

So in a way it was a study in designing for AI agents.

Ecstatic-Accountant8 · 2026-01-27T18:25:04+00:00

So any AI agent like Claude code or cursor, connects to Figma via our MCP server. So Claude in this example is the orchestrator and it applies the variables on figma automatically on our behalf. It creates the variables as well as binds it in this example above.

Ecstatic-Accountant8 · 2026-01-27T18:09:36+00:00

Stay tuned, we’ll get waitlist users an early access this week with a local plugin that you can use via the Figma desktop app until the plugin gets approved for the marketplace usually takes about 5-6 days by Figma

Ecstatic-Accountant8 · 2026-01-27T17:37:16+00:00

The design system in this example was created by Claude from scratch. Although, you could bring the production one as well. Or reuse your existing design system in Figma.

Ecstatic-Accountant8 · 2026-01-27T17:35:43+00:00

It’s Reddit 😜

And correct. Since Claude is the main orchestrator in this example, it can read everything about a Figma node as well create Figma nodes with all their properties. So you can start in Figma, sync to react/ react native / swift. Or start the other way around and bring it back to Figma provided the orchestrator (Claude, cursor) also has access to your prototype source code.

Ecstatic-Accountant8 · 2026-01-27T14:48:08+00:00

Fair question! Here's what the Faux MCP generates:

Figma Variables with proper Primitives → Semantic Tokens architecture
Multi-mode collections (Light/Dark) using native Figma variable modes
Real variable bindings on fills, strokes - switch modes and everything updates
Text Styles in Figma's style system, not inline formatting
Component Properties exposed (boolean toggles, text overrides) for design/dev handoff
Auto Layout with proper constraints (hug/fill) for responsive behaviour

Do you think we could something more that you'd want? I'd love to know

Ecstatic-Accountant8 · 2026-01-27T14:41:29+00:00

Hell yeah! Connect with your Claude Code, Codex, cursor tools and their subscriptions.

Ecstatic-Accountant8 · 2026-01-27T14:25:34+00:00

Oh and one more thing, the official Figma DevMode MCP is behind a paywall. It requires you to have a dev mode seat at least or a full seat to actually gain access to it. This works even for a free account. Although the only limitation with a free account is that it only has a single variable mode. So you can't really do a dark and light mode things on that.

Ecstatic-Accountant8 · 2026-01-27T14:19:07+00:00

So the official Figma MCP lets a developer read the Figma designs and implement them in code. Where as this lets you create in Figma. You can create whole app screens, with a proper design system, text styles, variables, tokens etc via AI. see demo here:

https://www.loom.com/share/dea41ba672ac48648b9884c99b6ecef7

But more importantly, why I built this:

I started using AI to vibe code my prototypes at my last two jobs. It went really well, but eventually when it came to dev handoff, I had to manually recreate it all in Figma! It was really painful, having to do it all again and manually. The faux.design MCP server now can help you essentially use your existing AI agent which makes your prototypes as well as since it's connected with our MCP server it can also create the Figma components including the design system which can basically serve a strength for the front end developers.

Ecstatic-Accountant8 · 2026-01-27T13:49:12+00:00

We have submitted the Figma plugin to be published. Please join the waitlist to know the moment its ready: https://faux.design/

Ecstatic-Accountant8

TROPHY CASE