Concepts

Concepts

Background reading on the problem Riyar is being built for. Three pages, no product tour.

A design system is not a library of components. It is an agreement about how a product looks and behaves, and an agreement only holds while someone can point at where it is written down. Most teams cannot point anywhere. The agreement is spread across a Figma file, a token file in a repo, a brand PDF, and the memory of three people who were in the room when it was settled.

That was survivable while every reader was a person. A designer could ask. An engineer could open the last screen that shipped and copy what was there. The gaps got filled by the same conversations, over and over, and the cost was paid quietly by whoever kept answering. Companies pay people to keep a single source of truth alive and communicated across the team. That work is manual, constant, and invisible until it stops.

AI writes production UI now, and it changes what the gaps cost. A tool cannot read a Figma comment, ask in a thread, or infer the reason behind a rule. It generates from nothing: no rules, no tokens, no approved assets. Given nothing, it invents something plausible — a grey close to yours, a radius close to yours, a button that is nearly right. Every tool gets re-taught the same system by hand, and the output still drifts.

The unit of the system

So the question is what, exactly, gets written down. The answer these pages work from is three layers. Decisions: the rules and their reasons — usage, tone, spacing — written once. Tokens and assets: the material — type, color, logos, components — held in one place and versioned. Those layers are the unit of the system. Small enough that a team can keep them current, complete enough that a page a person reads and structured context a tool pulls can both come from them without either going stale.

Join the waitlist