For AI agents: the documentation index is at /llms.txt, and any docs page is available as Markdown by appending .md to its URL.
Introduction
Every team ships UI faster than your design system can follow. Agents too. Shelf puts one registry in every product as plain source, and tracks every change.
Components land in your codebase as plain React files that your team and your agents can change or delete. Shelf keeps a hash of each file as installed, so it can tell your changes from upstream changes and merge the two.
Why
Every team ships UI faster than a design system can follow, and now agents do too. Each product drifts onto its own version of the system. Shelf is one registry, many owned copies, and a record of every change. It is open source under the MIT license.
Companies with more than one product usually end up with one of two setups. A shared component package keeps products consistent, but its API decides what a product can do: even a spacing or color change becomes an override that breaks on upgrade, or a request that waits on the system team. Copied files remove that wait, but after a few edits nobody knows what the original was, and fixes stop reaching anyone.
Shelf keeps the connection of a package and the ownership of copied files. Every product starts from the same source, and files nobody edited stay identical and update as-is. When a product does change something, the change is deliberate and visible: Shelf knows what each product installed, what it changed, and which updates it hasn't taken.
Why source
Engineers and agents change the implementation directly instead of working around an API. Hard interaction behavior stays a dependency: focus, keyboard, and ARIA come from Base UI, and styles compile with StyleX. What you own is the product-facing layer on top.
Designers work from the same components too: in the browser, in Storybook, or in code with an agent. Figma is optional: a plugin builds a native library from the same source. See the designer guide.
What you get today
106 components, 12 blocks, 3 patterns and templates, and semantic foundations with light and dark themes. A CLI with init, search, add, status, diff, update, and check for each product, and build and usage for the team that runs the registry. The roadmap lists what is available and what is planned.
Where to go next
Install Shelf in a project, read how ownership and provenance work, or see how agents use it.