Introducing Humic

I'm excited to finally share what I've been building. It's called Humic.

Earlier this week I posted about the disconnect between design and engineering. It's been a personal struggle for years, and I've watched it go wrong in a dozen different ways. One of the most stubborn? Design systems, and more specifically: tokens.

Tokens matter. They're a shared language, the thing that's supposed to let designers and engineers call the same thing by the same name. But here's what I keep seeing in the wild: the names drift. The values behind them change. And suddenly everyone thinks they're speaking the same language, when they're not.

Tokens are living things. They evolve as your product evolves, because they're the building blocks of it. You add more, you split things apart, you refine. But designers live in Figma, engineers live in the codebase, and the two slowly fall out of sync.

And then there's AI. AI needs a source of truth too.

If you've ever asked AI to build something in your style, your design, your system, and it came back looking nothing like your product, you already know the problem. Without the right tokens and guidelines, your agents are guessing. And guessing doesn't ship.

That's the gap Humic closes. One source of truth for your tokens: synced to Figma, available in your codebase, and readable by your AI agents. Designers, engineers, and machines, finally speaking the same language.

Humic is still in development. I'm looking for individuals and teams who want to get in early and help shape it with their feedback. If that sounds like you, join the waitlist or just message me directly.