Hey Product Hunt! I’m Luke, the maker of Zaklad. Started as a tool built for myself. Ten years working on design systems from both sides (design and dev) and the same problems kept repeating: Figma drifts from the code, tokens drift across platforms, and a huge amount of effort goes into just keeping things aligned and rebuilding bespoke pipelines every time. A design system isn’t optional. Every product ends up with one eventually, whether you planned it or not. The question is whether you build it deliberately or inherit a mess of inconsistent components and tokens that nobody owns. It’s also not something you want to vibe-code your way through: the decisions compound, and getting them wrong early is expensive to undo. Until now, doing it properly meant a dedicated team. Most teams don’t have that. Most tools treat Figma as the source of truth and translate downstream, with development as an afterthought. I wanted to flip that model: a token layer sits above both, and the Figma library and the component package are peer outputs of the same source. Nothing to keep in sync. Define your tokens, themes, typography, icons, and components in one place. Out the other end, a cross-platform npm package (React + React Native) and a real Figma library, versioned and generated from the same source with the pipelines set up for you. That’s what I mean by democratising it. One person can now give design and dev teams a proper, production-grade design system. That used to be a dedicated-team job. For context: tech lead on the design system at the largest company in the country I reside in (under NDA), previously worked on the Adidas and Reebok systems. Designer turned developer, which is why the tool is built the way it is. It’s early but it works. I’d love for people outside my bubble to try it and tell me what’s broken, what’s missing, and what’s right. Happy to answer questions here.

zaklad

Democratising design systems

Democratising design systems