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 know what level of complexity you’ve seen in your software buildouts, but at anything “enterprise” scale, building your own components from scratch is a recipe for absolute disaster. There are so many nuances, especially with accessibility, and edge case bugs, that I would really strongly recommend against it. And by extension, I’d be against this approach.

Maybe you could make it work if everyone agrees on a base set of headless components to use, but we seem to be moving in the opposite direction with things like ShadCN.