There are a lot of shadcn/ui libraries now. Most look good in a screenshot. The differences show up later: when your coding agent invents props, when a licence blocks client work, or when you need a data grid and the library stops at buttons.
These are the nine questions I'd ask before picking one. They work for any library. I'm on the ReUI team, so ReUI's own answers are in one section at the end, kept apart from the questions.
1. Does it extend shadcn/ui, or replace it?
shadcn/ui works because the code lands in your repo and you own it. A library should keep that deal. Check two things. Does the CLI copy source into your project, or do you import a package you can't edit? Does it read your existing theme, or bring its own?
2. Does it fit the primitives you already use?
New shadcn/ui projects default to Base UI since July 2026. Radix UI is still supported, and React Aria arrived the same month. A block built for one may not drop cleanly into another. Check which ones the library supports before you install anything.
3. Can your coding agent use it without guessing?
If you build with an agent, it will write UI from memory unless you give it something better. Memory means made-up props and a different look each time. Look for a registry the agent can install from and an MCP server that hands it the real component APIs.
4. Does it cover the hard components?
Buttons and cards are easy, and shadcn/ui already has them. The time goes into data grids, filters, kanban boards, calendars and gantt charts. Check whether the library ships these, and whether they're free.
5. What is free, and under which licence?
"Free" can mean MIT, free for personal use only, or free behind a sign-up. Read the licence line, not the badge.
6. If you pay, what are the terms?
Three things to check: subscription or one-time, a fee per project or not, and whether client work is allowed.
7. Can you see a block working before you buy?
A static screenshot hides a lot: how a block behaves at narrow widths, in dark mode, in your theme. You should be able to check all three before paying.
8. Is accessibility built in, on every primitive?
Keyboard, focus and screen-reader support are hard to add after the fact, especially on grids and boards. Ask two things: what primitives is it built on, and do the custom blocks inherit the same keyboard and ARIA behaviour? Then test one with a keyboard.
9. How do you get updates?
Copied source is yours, and so is keeping it current. Nothing updates on its own. Find out how you pull a newer version of a block, and how you'll see what changed before you overwrite your own edits.
What you take on with any copy-paste library
- The code lives in your repo, so merging fixes after install is part of the job.
- An agent works from the context it has. A registry or MCP server gives it the real APIs.
- Free and paid parts can follow different release schedules. It's worth knowing both.
The checklist
| Question | What to look for |
|---|---|
| Extends or replaces shadcn/ui? | Source copied into your repo, your theme tokens |
| Base UI, Radix UI or React Aria? | Works with the one you already use |
| Agent-ready? | A registry plus an MCP server with real APIs |
| Hard components? | Data grid, filters, kanban, calendar, gantt |
| What's free? | The actual licence, MIT or not |
| Paid terms? | One-time or subscription, per-project fees, client work |
| Preview before buying? | Live, responsive, dark mode, your theme |
| Accessibility? | Keyboard, focus and screen-reader support on every primitive |
| Updates? | A clear way to pull new versions without losing your edits |
No library wins every row for every project. Pick the one that answers the rows you care about.
How ReUI answers these
Quoted from reui.io, so you can check each line yourself.
1. Extends shadcn/ui
The CLI copies the source files into your project, same as stock shadcn/ui, so the code lives in your repo and you can edit it freely.
Every component reads from your shadcn theme tokens (--background, --foreground, --primary, --radius, font family).
2. Primitives
The same block for either interaction model, so your existing shadcn setup is the one it drops into.
3. Coding agents
The ReUI MCP server connects your coding agent to the live ReUI registry.
It is free with a ReUI account: the first connection opens a "Sign in with ReUI" approval in your browser, and a free account is created in that flow if you do not have one.
4. Hard components
Data Grid, Filters, Kanban, Calendar, Gantt and more, headless and yours.
5. Free licence
Commercial and open-source use are both fine; only the premium blocks, icons, and paid templates need a license, and templates marked Free need only a free account, under the License on Personal terms rather than MIT.
6. Paid terms
ReUI is a one-time payment with lifetime updates.
Ship it in as many client and commercial projects as you like.
One purchase, no per-project fee.
7. Preview
Pro blocks give you the full live preview, responsive, dark-mode-toggleable and theme-customizable, so you can confirm one fits your design before buying.
8. Accessibility
Accessibility, keyboard, and ARIA baked in
9. Updates
Re-run the install command to pull the latest version of any block.