<aside> <img src="attachment:cefa1732-da6f-49ad-a205-09c06d89a7e1:IMAGE_2025-12-31_222741.jpg" alt="attachment:cefa1732-da6f-49ad-a205-09c06d89a7e1:IMAGE_2025-12-31_222741.jpg" width="40px" />
I’m a product designer exploring how AI-native products should feel, behave, and collaborate with people, beyond simply adding another AI button to the interface.
This Behavioral Design System is an early, evolving resource for designers, builders, and teams who care about making human–AI interaction clearer, safer, and more useful.
If this sparks something, come say hi.
</aside>
AI is quickly becoming part of almost every product experience.
But while we already have design systems for buttons, layouts, components, tokens, and UI states, we don’t yet have the same shared language for AI behavior.
<aside> <img src="/icons/dialogue_purple.svg" alt="/icons/dialogue_purple.svg" width="40px" />
These questions show up again and again in AI-powered products.
<aside> <img src="/icons/clear_pink.svg" alt="/icons/clear_pink.svg" width="40px" />
That’s the gap this system is trying to explore. Not another UI library. More like a shared behavior layer for human–AI interaction.
A traditional design system helps teams make interfaces consistent.