ReactTailwind CSS v4shadcn registry
A design system your AI builds with
Paste one link into Claude. It learns opendraft's components, tokens and design rules, then builds your screens from them instead of inventing its own.
143 components
From buttons to data tables, installed as source.
39 AI patterns
Chat, tool calls, approvals and thinking traces.
One theme file
Light and dark mode from the same tokens.
Docs AI can read
An llms.txt index and a plain page per component.
You describe the screen. Claude assembles it from opendraft.
Every example starts with the same opendraft link and a plain request. Pick one to see what Claude installs, the code it writes and the result.
You
A sign-in page with email and password, a “remember me” option, GitHub sign-in and a link to create an account.
- Read raw.githubusercontent.com/nuelmdesign/UI-System/HEAD/public/llms.txt
- npx shadcn add @opendraft/card @opendraft/input @opendraft/label @opendraft/checkbox @opendraft/button @opendraft/separator
- Wrote app/sign-in/page.tsx
One link turns Claude into an opendraft developer
Without it, an assistant guesses at your UI and every screen comes out a little different. With it, Claude works from the same parts and rules you do.
Share the link
Paste the opendraft prompt into Claude, or add the link to your project's rules file once.
raw.githubusercontent.com/nuelmdesign/UI-System/HEAD/public/llms.txtClaude reads the system
It learns how to set up a project, the design rules, every token, and what each component is for.
rules · tokens · 143 componentsReal components land in your repo
Claude installs them with the shadcn CLI and builds from them. The code is yours to read and change.
npx shadcn add @opendraft/cardEverything a product screen needs
The usual app components, plus the AI and data pieces most kits leave out. All of it shares one set of tokens.
71 core components
Buttons, inputs, dialogs, menus, tables and date pickers, built on Radix.
39 AI agent patterns
Streaming answers, tool calls, approvals and reasoning traces for chat products.
Data and workflows
Records tables, diffs, flowcharts and insight charts for internal tools.
One theme file
Every color, radius and shadow is a token. Change one and every screen follows.
Light and dark
Each token has a dark value. Any section can go dark with one class.
Shared motion
One set of springs and easings, so every component moves the same way.
Accessible
Keyboard and screen-reader support comes from Radix primitives.
Ready-made screens
Blocks for a CRM board, analytics, settings, sign-in and an agent chat. Install one and pass your data.
Source you own
No package to update or work around. The files live in your repo.
Your fonts, your colors, your corners
opendraft's look is a starting point, not a rule. Pick a heading font, a body font, a primary color and how round things should be. Copy the prompt and Claude applies it to every component, or copy the CSS and paste it in yourself.
Your theme
Invite your team
Teammates get an email with a link to join this workspace.
Use the opendraft design system for this. Read https://raw.githubusercontent.com/nuelmdesign/UI-System/HEAD/public/llms.txt first and follow its rules: install components from the @opendraft registry and style only with its tokens. If you can't run shell commands, fetch each component's file from https://raw.githubusercontent.com/nuelmdesign/UI-System/HEAD/public/r/<name>.json (each file's content is inside) and create them in the project yourself. Build: [describe what you want to build]
Change a setting above and the prompt picks it up. With the defaults, the assistant uses opendraft's own look.
Start from a working piece
Each component has a live preview, the code behind it and a one-line install. These are a good place to start.
Questions, answered
Something missing? Open an issue on GitHub and it'll be added here.
Using it with AI
Code
Cost and credits
Build your next screen with opendraft
Copy the prompt, tell Claude what you need, and start from real components.