Asterix vs shadcn: Which Is Better for AI-Built UIs?
Meta's Asterix vs shadcn for agent-built React UIs: nightly vibe test scores, Tailwind support, swizzle vs copy-in, bundle size, and beta caveats.
For Engineering and Design

Should you choose Asterix or shadcn when a coding agent builds your UI?
For most teams today, shadcn is still the safer pick, and Asterix is worth trying on a new React 19 project. Meta's own nightly tests show Asterix scoring higher on a good night (98 vs 95), but Meta also says shadcn wins the most nights across the full record. Asterix is in beta, needs React 19 or newer, and shipped a noticeably heavy demo page. If you start fresh and lean on agents, test Asterix. If you have a working app on shadcn, stay put for now.
TL;DR
- Asterix is Meta's open-source design system, grown over about eight years of internal use at the company. It is MIT licensed and in beta.
- Meta publishes nightly "vibe tests" where agents build the same UI prompts four ways. On a good night: Asterix 98, shadcn 95, raw HTML 82.
- The scores are not a clean win. Meta also published a bad night where Asterix fell to 77 because the agent invented imports and props, and says shadcn wins the most nights overall.
- The big difference is how agents learn the system. Asterix's command line tool is the documentation, so the agent looks things up instead of guessing.
- The costs are real. React 19 or newer, Node 22.13 or newer, a version 0.7 API that changes almost daily, and about 600KB of JavaScript (before gzip) on one demo page.
- If you already run a mature app on shadcn or MUI, waiting until Asterix leaves beta is reasonable.
What is Asterix?
Asterix is a React design system: a set of ready-made, accessible interface parts (buttons, dialogs, tables, forms, date pickers, an app shell) with full TypeScript types. Meta open-sourced it after using it internally for about eight years. It was released in beta in June and had around 18,700 GitHub stars at the time of the source review.
The README claims more than 150 components, and the command line tool (CLI) one reviewer installed listed 174. It also includes page templates and block templates: complete layouts such as a dashboard, login page, settings page, or AI chat screen.
Internally it uses StyleX (Meta's styling library), but you do not write StyleX. You import two pre-built CSS files and use the components. There is no build plugin, PostCSS setup, or Babel config.
What is shadcn, and why do agents use it so much?
shadcn/ui is a different kind of thing. It is not a package you install and import. You copy component source code into your project, built on Tailwind CSS utility classes, and from then on you own that code. Because it is so widely used, coding agents have seen a lot of it and tend to produce it competently.
That ownership is both the appeal and the cost. You can edit anything. You also maintain everything, and upstream fixes do not arrive on their own.
How does Asterix try to fix the "generic agent UI" problem?
Ask an agent for a UI with no guidance and you usually get a pile of divs, random hex colors, some Tailwind classes, and a layout that works but belongs to no system. Asterix attacks this in four ways.
- The CLI is the docs. The documentation website reads from the CLI, so there is one copy that cannot drift. Meta's blog post on this is titled "The Best CLI is One You Never Run," because your agent runs it for you.
- An init command writes rules for your agent. You tell it which agent you use (Claude, Cursor, Codex and others), and it adds a managed block to that agent's instruction file, such as CLAUDE.md. The rules: start every page from a template, avoid raw divs, avoid hard-coded hex colors and pixel values, look up a component before using it, and run the doctor command when finished.
- A build command picks examples instead of generating code. You describe a "settings page for a SaaS app" in plain English. It chooses the closest page template, suggests blocks, and lists components for the rest. Meta's reasoning is that AI copies, so give it good things to copy.
- Lookup commands stop invented props. You can search components, hooks, docs, templates and themes in one ranked list, or ask for a single component's exact props, variants and defaults. Commands can return JSON with stable error codes and a dense mode that saves tokens.
If you would rather skip the CLI, there is a hosted MCP server (a standard way for AI tools to call outside services) that gives the agent two tools, search and get, drawing on the same docs. There is also an llms.txt file on the site.
What do the vibe tests actually show?
Every night, Meta gives agents the same set of UI prompts and has them build with four setups: Asterix, Asterix plus Tailwind, shadcn plus Tailwind, and raw HTML. A separate judge agent scores the results. The tests live in the Asterix repository.
| Setup | Score on a good night |
|---|---|
| Asterix | 98 |
| shadcn + Tailwind | 95 |
| Raw HTML | 82 |
Read these carefully. The judge is another AI, the prompts are Meta's, and Meta runs the tests. Still, they published a bad night where Asterix dropped to 77 because the agent made up imports and props. They also say shadcn wins the most nights across the whole record. A vendor showing its own weak results is useful information, and it tells you the gap between the two is small and varies run to run. A 3-point lead on a good night is not a reason to migrate.
The 82 for raw HTML is the more practical number. Any design system, with agent guidance, beats having the agent write markup from scratch.
How do Asterix and shadcn compare in practice?
| Asterix | shadcn/ui | |
|---|---|---|
| How you get components | Install as a package | Copy source into your project |
| Customizing | Pass a className (Tailwind, CSS modules, or plain CSS), or change theme CSS variables | Edit the code you own |
| Full control | Swizzle command copies one component into your project | Already yours |
| Upstream fixes | Arrive for everything you have not swizzled | You merge them yourself |
| Agent guidance | CLI, init rules, templates, MCP server | Whatever your agent already knows, plus your own rules |
| Maturity | Beta, version 0.7, releases almost daily | Widely adopted |
Swizzle is the clever middle path. It is shadcn-style ownership, but only for the components you choose to change. The rest keep getting upgrades.
Theming is also straightforward: a theme is a set of CSS variables, so you can restyle the system without forking components. Themes mentioned include neutral, butter, chocolate, stone, gothic and Y2K, and dark mode is built in.
What are the downsides of Asterix?
The source review was candid about these, and they matter.
- Beta software. Version 0.7, with new releases almost every day. Expect breaking changes.
- React 19 or newer, and the CLI needs Node 22.13 or newer. An app still on React 18 is out.
- Theme maintenance. Only the neutral theme is marked as maintained. Every other theme is a separate package you install first.
- Charts are not stable. The charts package is only on the Canary channel.
- Swizzling has a catch. Once you swizzle a component, your build needs a StyleX compiler, or that page will not render.
- Strict agent rules. "No divs, no raw hex values" produces consistency, but a team that lives in Tailwind utility classes must decide how much of it to follow.
- Bundle size. One demo settings page came out around 600KB of JavaScript before gzip. That is one data point, not a benchmark, so measure your own pages.
- A naming trap. Before the CLI is installed in your project, running plain
npxwith the short name points to an unrelated package. Use the full package name from the Asterix docs until it is installed.
Is Asterix worth it for you?
New React 19 app, heavy agent use: Try it. In the review, the templates and build command visibly changed what the agent produced on the first page. A full settings page with sidebar, forms, toggles and spacing took a few minutes, mostly waiting on npm install.
Mature app on shadcn or MUI: Wait, or trial it on a side project. Migration cost is high and the API is still moving.
Performance-sensitive or React 18 project: Skip it for now.
Not a developer, but you commission UIs from an agent: Ask whoever owns the codebase which setup is in use. The practical lesson from the tests carries over: agents do better when they have a system, examples to copy, and rules written down in the project.
A low-risk way to test: build one internal page (a settings screen, say) with each setup, using the same prompt, and compare how many invented props or imports you have to fix.
Do you need to wire up a design system at all?
If your goal is an internal tracker, dashboard or request form rather than a UI library decision, you can skip choosing one. Remy builds and deploys a full-stack app from a plain-English description, and a build includes a design system alongside the database, sign-in and hosting. A manager who wants an approvals form or a team dashboard could describe it and get a working app, instead of weighing Asterix against shadcn. Developers who want to pick their own component library can still do that in a standard TypeScript git repo they own.
Frequently Asked Questions
Is Asterix better than shadcn?
Not clearly. On a good night in Meta's tests Asterix scored 98 to shadcn's 95, but Asterix also had a 77 night, and Meta says shadcn wins the most nights across its full record. It is a promising, beta-stage alternative, not a proven upgrade.
Does Asterix work with Tailwind?
Yes. You customize components by passing a className, which can be Tailwind, CSS modules, or plain CSS. Meta also tests an "Asterix plus Tailwind" setup. Its agent rules discourage raw divs and hard-coded values, so Tailwind-heavy teams need to decide how strictly to follow them.
Which agents does Asterix support?
The init command supports Claude, Cursor, Codex and a few others by writing rules into that agent's instruction file. There is also a hosted MCP server with search and get tools, and a global init that installs a skill so every project already knows Asterix.
What do I need to run Asterix?
React 19 or newer and Node 22.13 or newer for the CLI. It is MIT licensed and in beta at version 0.7. Only the neutral theme is marked as maintained, and the charts package is only on the Canary channel.
Useful for
How we source, write, and correct our articles. Editorial standards
Related articles

What Is Design Arena? How AI Creative Benchmarks Work

How to Set Up Meta's Asterix Design System With an AI Agent

How to Design Hardware With Claude Fable 5.2, Step by Step
