Randr documentation
Randr keeps a brand's tokens, guidelines and assets in one workspace. A team reviews and publishes them as an immutable release, and people, pipelines and agents read exactly that release.
These pages are for the people who connect Randr to their tools: agents such as Claude Code and Codex, CI jobs and repositories. The design system the app is built with is documented at the end. What changed recently is in the changelog.
Agents and MCP
- Connecting agents and CI
Claude Code, Codex and GitHub Actions, with read-only credentials by default.
- Randr CLI
Pull approved, checksummed assets and tokens into a repository.
Reference
- Design tokens format
The W3C design tokens JSON that Randr imports and exports.
- randr.config.json and randr.lock.json
How a repository declares the assets it uses and pins their revisions.
Design system
- Principles
Tokens first, one edge one line, motion by frequency, keyboard first.
- Foundations
Colour roles, type, space, radius, shadows and motion, read from the token files.
- Components
Every primitive and pattern, rendered live with its variants and sizes.
- Layout and data
Shell sizes, breakpoints, panels, tables, lists, empty and error states.
- States and accessibility
Status, request states, contrast, keyboard and reduced motion.
- Implementation
Where things live, the composition rules and the tests that guard them.
- Motion rules
Which element moves, how long, and when nothing should move at all.