What if your design system could explain itself?

Why does Button have those specific variants? Why doesn't Card support custom backgrounds? The answers are buried somewhere—a Slack thread, a PR comment, the memory of someone who left last year. We're building the thing that remembers, and tells you what needs attention before you have to ask.

For design system teams who are tired of explaining the same thing twice.

The knowledge drain is real

  • Design decisions live in Slack threads nobody searches
  • The person who knew why ships to a new company
  • "Why does this work that way?" becomes "I don't know, let's just add a prop"
  • You find out about accessibility regressions from users, not tools

How it works

  1. 1
    Connect your component library

    Your code, Figma files, Storybook stories—wherever your components and tokens live.

  2. 2
    AI agents analyze and capture context

    They read your components and tokens, understand relationships, and preserve the reasoning behind decisions.

  3. 3
    Ask questions, get proactive insights

    Get answers with citations. Know your system's health without having to ask—what needs attention, and the impact of changes before you make them.

We're building this with you.

Gotrino is approaching alpha. If you maintain a design system and want early access, join the waitlist.

No spam. Just updates when we have something worth sharing.