Launching today
Balsa UI
Create design systems, build with agents
72 followers
Create design systems, build with agents
72 followers
Balsa establishes a clear contract between your design system and a powerful UI library. Its registry delivers the source code your agents can use, extend, and evolve.
this is basically the shadcn model (source code delivered into your repo instead of an npm black box) but pointed at agents instead of humans copy-pasting, which feels like the right instinct given how much agent-written UI code I've seen drift from whatever design system it started from. the question I'd actually want answered before adopting it: once an agent has extended a delivered component and the registry ships an update upstream, what's the story for reconciling the two? shadcn's answer is basically "you're on your own, diff it yourself" - curious if Balsa has anything smarter than that or if it's the same tradeoff.
Balsa UI
@galdayan Hey Gal! Good to know you're using Balsa! That agentic focus really is what I'm trying to achieve with it.
Balsa currently has npx balsa-ui@latest diff <component>. It compares the originally installed source, your local copy, and the current registry version, then reports whether it’s unchanged, local, upstream, or diverged. It currently stops at that classification.
Thanks for raising the gap. 0.8.1 is being published now. The command will also print unified file-level diffs from local source to registry source, and the Balsa agent skill will explicitly instruct agents to run it before updating. Automatic updates will still preserve local and diverged files unless replacement is explicitly forced.