Thoughts and feelings around Claude Design

Then I looked at the usage and it said I had used 95% of my Claude design usage for the week!

This isn't a real tool. This is a plaything, if that's what they're providing as examples.

Building the same design system component in code versus in Figma is going to be slightly more succinct in code; Figma’s primitives don’t have the sort of conditionals and control flow that code has. But code is much less malleable than drawing on a screen, and creative freedom is harder to achieve in code.

UI can fix the gap where code feels less malleable than Figma, but complexity comes largely from the worlds that humans create, and humans apparently want to create 8 modes for 4 products and 2 light/dark modes. If you want the same setup in Claude, it’ll be a little easier to maintain, but not much less complex.

This article is a fundamental misunderstanding of both the design space, and figma as a company.

Just a few of my thoughts:

- Figma was always about building a successful company over a successful product. Figma started with a much more ambitious aspiration, and had the ability to deliver through talent like Evan Wallace. A lot of it started with showing how capable webgl was in the browser. And yet, a lot of things like 3d features don't exist because they had the awareness to really hone in and focus on building a specific thing that made them money because everybody in the company ended up with an expensive seat price.

- Seriously, Figma is a company that's about design tool second, and about getting a product that businesses use first. To that end, it's already succeeded through the IPO, subsequently, who knows what the market is going to look like. Figma having a war chest is in many ways much better than having a technically impressive demo that might evaporate.

- People at Figma, 100%, know everything in this article. And not just figma people, like anybody and everybody that's tried to build a design tool has had these thoughts. It's very obvious that ui/ux is the interesection of design/dev/pm. It's also very obvious that it should stick close to the source of truth, to something like code. - The problem is, that it's almost underselling it to say that it's MASSIVE challenge to execute on these ideas because of how easily it bleeds into building not just a design tool, but a coding, data management, architecture, etc. tool

- I could talk at length about all the challenges and potential solutions, but that's neither here nor there.

- On AI, I guess other people's guess is as good as mine, but my gut feeling is that while data is important, SOTA AI is generalist enough that the base models, the thinking they're able to do, is better than having a lot of custom data. Especially because ui design is front-facing - you can just scour the web in contrast to private financial documents, or legal documents for example.

I was wondering if PenPot (https://penpot.app) might be sitting pretty in this new agentic era, considering that they took the direction of designs being actual markup, unlike the canvas approach in fig - if that’s even something that interests them.

> Figma accidentally excluded themselves from the training data that would have made them relevant in the agentic era.

Their binary format is so much of a "let's reinvent everything" which I think come from the fact it's a tool you can use for web design, android app design, ios design and anything-you-want design that it became a jack of all trade and so mapping it to web is not a perfect 1:1 translation.

And for being useful to agent, any people who got to implement the figma from a UX guy know that even human can't know truly the intent of most figma design, so how a LLM could ? Common source of question that even the UX guy has no answer for:

  1. Ok this button looks great, but in German how will it look ? 
  2. Oh and actually this button does not look great when i put in CSS, it wraps on two line, you cheated again with the letter spacing, did you ?
  3. How does it look on a phone that is not an iphone ? 
  4. You know that doing a border with a gradien is not possible in CSS, so what should i put ?
  5. How does it look on a 4k screen ?
  6. etc.

So I can't wait for these tools that are html behind to catch up, even more if we can have the prompt with it. (As a developer I never got to see the prompt the product manager made to the UX guy)

[0]https://github.com/allan-simon/figma-kiwi-protocol

But the fundamental problem is that it’s hard to get a design system right long-term, especially because it’s so intertwined with your code and whatever component library you use, which is a layer your designer will never touch. I don’t really see Claude Design fixing the fundamental Storybook hell of designing reusable and pretty components and layouts, but I don’t see Figma or any other tool solving it either.

What’s the solution? It feels like something that needs to be fixed more deeply at the component level.

https://stitch.withgoogle.com/

Claude Design - https://news.ycombinator.com/item?id=47806725 - April 2026 (732 comments)

But I think it's part of a larger mistake Figma is making: they seem to have shifted to an extraction mindset too early, assuming they'd captured the market, right when the ground beneath them is starting to shift.

It's most visible in their pricing model evolution, which is now explicitly anti-collaboration. Figma used to be the obvious default because you could quickly share files with non-designers, so they could view and make small edits without fuss. Now that requires a paid "seat", along with a confusing mess of permission flows.

It's platform wide too. I taught a college design class recently, and had students sign up for Figma because it seemed archaic not to teach them to use it. Instead of just giving any ".edu" address a free account (like they used to) students are forced through a 3rd-party process of uploading transcripts to prove education status. A few of my students got rejected or ran into confusing errors, and never got access… Now I have to re-evaluate whether its worth using when teaching the class again. (And this is for a population with near-zero short-term purchasing power, but huge potential long-term value… why add barriers?)

This is such a weird self-inflicted wound for a collaboration platform to make. The big tools that won on collaboration (eg. Google Docs, GitHub) have understood that low-friction sharing is critical to becoming the default choice. And that being the default is a flywheel that drives adoption, both in users and in tooling.

It makes more sense if you see it through the lens of Figma trying to juice short-term numbers for their IPO. But it's sad to see because it had so much long-term potential.

What Figma achieved technically in the 2010s was amazing. Coded the app in C++ and then used WASM to deliver it as a multiplayer web app.

But now it's trying to be too many things. Why did they ever feel the need to add slides and this other stuff.

Their MCP is poor (sure, they'll improve it).

The app struggles with larger files and performance is sloppy.

And don't get me started trying to design data grid heavy apps.

And they could easily follow Adobe's lead. Enshittify and lock you out of your account whenever they feel it's necessary (remember what happened with Venezuelan Adobe users a few years ago?)

Either Penpot gets their act together and will become the opensource design canvas for open-weight AI models or we will see another open source solution that will fill this space.

I have a complicated nextjs webapp, and I havent had to write front end code in six-nine months now.

I suppose that a layout engine made sense in the context of Flash, and you saw the future of the web as a set of keyframe animations. But the notion that there's a lot of value in creating a very heavy, high-friction abstraction between the UI/UX and the platform it ultimately runs on was always going to be a loser.

In the end, it turns out we're all just web developers, regardless of your weapon of choice.

And here I am with Claude Code... That so far generated a 2000-line CSS file for a 7000-line app consisting of literally three web pages [1]. Where almost every single color, component, class and style is duplicated at least two times. Where custom classes are fighting with Tailwind classes (yes, there's also Tailwind ON TOP of custom CSS) that are fighting with inline hardcoded style= declarations.

Figma is definitely going to suffer the vibe-coded design slop-app from Anthropic.

[1] 7k lines are almost justified for the functionality in them, and I tried to keep an eye on the code. It's harder to keep an eye on CSS