Design System
Code-first system so designers, engineers, and agents ship the same UI.
Problem
Exchange UI was getting rebuilt ticket by ticket. Designers were not on every pull request. Coding agents filled the gap by inventing components Limitless does not ship. Prototypes and the product diverged.
An agent with no rule for the real component invented one. The prototype looked settled. Production did not match it.
Built
A dual-platform design system, React and Flutter, with one path from capture to code.
Figma capture, then a frozen pack, then generated visual cores, then hand wrappers, then Storybook.
New work starts as a candidate in the repo. Designers approve it in Storybook and promote it to core. About 28 React cores are in today: button, input, card, drawer, sheet, table, and more. The candidate backlog is larger.
Shipped. The system is live on both platforms. The capture pipeline and the promotion path are in place. Road-to-main finished in August 2026.
Tokens
Color, type, and spacing are the shared language. Components come after them.
The same Button
One Button, drawn as a Figma atom and reviewed as an Interactive story. Engineers and agents read that story before a designer promotes the component.
Core and legacy
Storybook groups what is already in the system: Tokens, Atoms and Molecules, Legacy components that need designer review, and Workspace.
New work starts as a candidate in the repo. That path is not a Storybook group. Designers approve the candidate in Storybook and promote it to core. Legacy is the review queue for components that still need designer review.
Agents and engineers resolve the design system, then candidates, then legacy, before inventing UI. That order is an AGENTS.md rule, not a sidebar label. AI Ready means the rule. Unresolved beats invented. The Figma pack beats memory.
In product
An Exchange screen built from the packages. The system in use, not a second kit beside the product.
For whom
Designers promote in Storybook. A candidate becomes core only after that review.
Engineers and coding agents walk the same ladder before they invent a component: the design system, then candidates, then legacy. Product UI and prototypes both pull @limitless/ui.
PMs review prototypes. They do not author components in Storybook or from @limitless/ui.