Figma's woes compound with Claude Design

Post by bcjdjsndon » Tue, Apr 21, 2026, 11:55 AM UTC

jmull wrote: post #40

Not sure Claude Design really competes with Figma. While it has a strong potential to let people iterate on using a design without the nuts and bolts of going back and forth with a designer, CD operates at the "leaf-node" level, where the output is generated. However, a lot of design has a deeper life-cycle than that. There's the collaboration, pitching, review, iteration, asset management, etc. In fact, the first st…

Post by sgarrity » Tue, Apr 21, 2026, 2:03 PM UTC

jmull wrote: post #40

Not sure Claude Design really competes with Figma. While it has a strong potential to let people iterate on using a design without the nuts and bolts of going back and forth with a designer, CD operates at the "leaf-node" level, where the output is generated. However, a lot of design has a deeper life-cycle than that. There's the collaboration, pitching, review, iteration, asset management, etc. In fact, the first st…

Post by [deleted] » Tue, Apr 21, 2026, 5:07 PM UTC

troupo wrote: post #80

coldtea wrote: post #71

Earlier quoted context omitted.

> It still produces subpar code, with horrendous data access patterns, endless duplication of fucntionality etc Not really. 2024 called.

Just because you don't look at the code, doesn't mean it doesn't produce subpar code constantly . Opus 4.7, high effort. Literally 30 minutes ago. There's a `const UNMATCHED_MARKER = " "` that we want to remove from a file. Behold (the first version was a full on AST walk for absolutely no reason whatsoever, by the way): function restoreUnmatchedSelectors(cssPath) { const cssContent = readFileSync(cssPath, "utf-8");…