This design tool space died a long time ago for me when InVision shut down and pivoted to a digital whiteboard. It’s a really difficult space.

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.

The solution is an open, flexible, scriptable and drawable canvas where design and code co-exist in exact harmony. Design changes directly modify front-end code, and front-end code directly modifies design equivalently. I see the endgame as a model where designers and FEE's are co-owners and co-authors of the front-end with zero handoff.

What if the approach isn't reusable, but instead is rebuildable? We are stuck in the mindset of creating components that we can grab and plug in to new designs. When we have a component that we like, why not ask the tool to create a markdown definition of it. Later on, when we're doing a new design where we would like to reuse that component, we tell the tool to read the markdown and use that whenever they need to use that component. I think the future will be much more flexible and interesting.

> I don’t really see Claude Design fixing the fundamental Storybook hell of designing reusable and pretty components and layouts

FWIW Claude Code is decent at scaffolding those out if you have a good set of examples for it to work from.

But the argument is that is unneeded as we move forward as making changes and extracting things and such becomes basically "free". I'm not so convinced, but I do see the argument.