👋 hey, I'm Ark — an engineer who builds systems
Give a language model my component library and it stops guessing. Same design, same tokens, same clean code — whether it's a fresh chat, a new feature, or a teammate who's never seen the system before.
// the one-liner
Developers already trust component libraries — Bootstrap, MUI, Tailwind. You pull them in, and everything looks right without thinking about it. I build the same kind of library, with one difference that changes everything: it governs what AI is allowed to generate, too.
Engineers get the library they already know how to use — drop-in components, typed props, clean architecture they can merge without a second look. But it isn't only for engineers: PMs, designers, and anyone who wants to build a feature or make a change can prompt against it and get real, on-system code back. And every AI tool pointed at it produces output that already fits. One source of truth for people and machines alike.
"Design consistency stops being a rule people have to remember. It becomes something the system enforces on its own."
// where it earns its keep
Consistency isn't impressive in a demo. It's impressive on the hundredth prompt, six weeks later, from someone who's never seen your design system.
Normally, "make it a bit tighter," "no, the other blue," "smaller radius" — you nudge the model ten times and still babysit the output. With the library, there's nothing to nudge. The tokens are the only values it can reach for.
Fresh context, zero memory of yesterday's rules. A raw model starts guessing from scratch and drifts. Mine doesn't carry the rules in the conversation — they live in the library, so a new chat is already caught up.
Different person, different prompt style, same deadline pressure. This is where design systems quietly rot. Here, their AI is pointed at the same library as yours — so their feature lands on-brand without a single design review ping.
Left alone, an LLM will happily hallucinate a shiny new dropdown that doesn't exist in your system. The contract won't let it. It has to compose what's already there — no phantom components, no one-off styles to clean up later.
// see it happen
Both sides were told: "a primary action button." The only difference is whether my library is in the loop.
// the contract — it picks intent, never raw values
interface ButtonContract {
variant: "primary" | "secondary" | "ghost"; // no free-form color
radius: typeof tokens.radius.control; // on-scale, or it won't compile
spacing: typeof tokens.spacing.control;
}// the receipts