There’s a moment in every design system’s life when the people who built it start to forget why.

Why does Button have those specific variants? Why doesn’t Card support custom backgrounds? Why did we decide against that prop three years ago?

The answers exist somewhere—buried in Slack threads, lost in old PRs, scattered across Notion docs that nobody updates. And when new team members ask, we do our best to reconstruct the reasoning. Sometimes we get it right. Often we don’t.

What if your components could explain themselves?

That’s the question that started Gotrino. Not “what if we had better documentation” (we all know that’s not the real problem). But what if the system itself could surface the context, the constraints, the reasons behind every design decision?

We’re building AI agents that read your actual code—your component implementations, your TypeScript types, your Storybook stories, your Figma files. Agents that understand not just what a component does, but why it was built that way.

Evidence, not hallucination

Here’s the thing about AI and code: the temptation is to let the model fill in the gaps. To generate plausible-sounding explanations that might or might not be true.

We’re taking a different approach. Every answer Gotrino gives includes citations—whether that’s a scan result, a source file, or a piece of documentation. You can see where the information came from. Trust, but verify.

Proactive, not reactive

Most design system tooling waits for you to ask. We think that’s backwards.

Gotrino monitors the health of your system—tracking token usage, component adoption, accessibility patterns, and documentation coverage. When something drifts, you’ll know before it becomes a problem.

And when you’re about to make a change? Impact analysis shows you what breaks. Change a token value, and see every component across every platform that uses it. Modify a component prop, and understand the downstream effects before you ship.

Design systems span code, design tools, and documentation. Changes ripple across all of them. Gotrino helps you see the full picture.

What’s next

We’re approaching alpha, building out the core agent system and testing it against real design systems. If you’re maintaining a component library and want to help shape what this becomes, join the waitlist.

More soon.