Define
Rules and decisions, written once. Usage, tone, spacing, and the reasons behind them.
01 Problem
The newest members of your team can’t read Figma comments.
AI writes production UI now. It generates from nothing: no rules, no tokens, no approved assets. Every tool gets re-taught the same system by hand, and the output still drifts.
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.
02 System
One source of truth, served two ways.
Hold
Tokens and assets, versioned. Type, color, logos, components, in one place.
Serve
Documentation for people. Structured context for AI tools through MCP and API.
03 Flow
Your system in the middle.
Designers, engineers, and the brand team read from Riyar. Riyar serves coding agents and generative tools. The same rules reach Figma, code, and docs, where the work happens.
04 Questions
What people ask.
What is Riyar?
Riyar is hosted documentation for design system teams. One place where your design decisions, tokens, and assets live. People read it, and AI tools build with it.
Who is it for?
Designers, engineers, and brand teams, who read the system and keep it alive. And the coding agents and generative tools that now build production UI from it.
How do AI tools use it?
Through MCP and API. That is the Serve module, and it is being built: structured context, so a coding agent or a generative tool works from your rules, tokens, and approved assets instead of from nothing. It is not open yet.
How is this different from a Figma file or a docs site?
A Figma file holds the drawing and the comments that explain it, and a docs site holds the prose. Riyar holds decisions, tokens, and assets together, across Figma, code, and docs. And the same source is being built to serve AI tools through MCP and API, not only readers.
What is the status, and how do I get access?
Riyar is in development. The waitlist is the way in: leave your email at the bottom of this page.