What Would You Want From AI That’s Forced to Use Your Component Library?
Most AI UI tools are fun until they hit reality:
Your design system.
They generate layouts that are:
off-brand
off-component
off-token
and definitely off-roadmap
So I keep coming back to this alternative:
AI that can only design with components from your library.
Imagine connecting AI to your real system and it learns:
your tokens
your components and props
your patterns
your rules
No inventing new buttons.
No “creative” typography.
No random spacing logic.
What should this kind of AI actually do?
If AI truly understood your library, what should be the first job you give it?
Generate on-system first drafts?
Refine existing screens to improve hierarchy?
Create states (empty/loading/error) using approved patterns?
Help migrate old UI to modern components?
Flag off-system usage and suggest fixes?
I’m seeing early signals that this could be a massive unlock for large teams - but I want to know what would make it genuinely valuable for you.
Questions for you 👇
What is the #1 task you’d trust a system-first AI with?
Where would you still require human review every time?
Would you use this more for creation, refinement, or governance?
PS: We've been a little quiet on here, but we will be launching very soon! Be sure to follow so you don't miss out!
Replies