Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Astryx

Meta's open-source React design system, with a CLI built so coding agents can look up components and build pages the same way people do.

Reviewed by ReviewRamble editors · Updated

View on GitHub Open source

Our rating

4.0/5

A mature component library with an unusually agent-friendly CLI, worth adopting for a new React 19 app, though its beta label and 0.x version mean breaking changes are still part of the deal.

What is Astryx?

Astryx is Meta's React design system, used inside the company for eight years and, by Meta's count, in more than 13,000 internal apps, now published under the MIT licence. It ships 150+ accessible components, seven themes, dark mode, page templates and a CLI. Styles are authored with StyleX but shipped as pre-built CSS, so you import it with no build plugin and override with Tailwind, CSS modules or plain CSS.

The AI angle is the CLI. astryx search, component, docs and template print component props, tokens and templates as text or typed JSON, with a --dense mode that cuts tokens; astryx manifest --json describes every command so an agent need not scrape help text; astryx init writes a managed Astryx section into your agent docs and can install a skill for every coding agent on the machine. The docs site's llms.txt tells agents to use the CLI rather than crawl pages.

The repository was created in January 2026, has about 24,850 stars and 1,941 forks, and is still labelled beta; v0.7.14 shipped on 11 November 2026. @astryxdesign/core had about 635,000 npm downloads in the week to 10 November.

Is Astryx worth it?

Astryx is first a design system and only second an AI project, and that ordering is its strength. Eight years of internal use at Meta means the 150+ components cover table pages, form wizards and detail layouts that newer kits leave to you, and the accessibility work comes with them. What makes it relevant here is that Meta designed the API, docs and CLI together so that an agent building a page gets the same reference a person does.

In practice that means an agent can run astryx component Button --json or astryx search "date range" and get typed, versioned answers from the installed package rather than guessing props from training data. The --dense flag returns compact text to save context, and astryx doctor checks that your agent docs still carry the Astryx section after an upgrade. This is a more reliable loop than pointing an agent at a docs website, and it is the part rival libraries mostly lack.

The trade-offs are the usual ones for a young public release of an old internal system. It needs React 19 or later. The version is 0.7.14, releases land several times a week, and 679 open issues and pull requests show how much is still moving; upgrade codemods exist because APIs change. Charts are published only under a canary tag. Swizzle copies a component's source into your project when you need full control, which also means you own its upkeep from then on.

There is little to worry about on data: it is a front-end library with no service behind it, and the CLI's only network behaviour described in the README is telling you when a newer version is out. For a team already settled on shadcn/ui, the upgrade command can refresh copied components, but moving a mature app across is real work; the stronger case is a new internal tool where agents will write much of the UI.

Where it earns its place

  • A three-person internal tools team using Claude Code

    Build admin dashboards that look consistent without a designer

    Run astryx init so the agent docs point at the CLI, then ask the agent to scaffold a table page from a template. Free; the time saved is in fewer rounds of fixing invented props.

  • A front-end lead at a 40-person SaaS company

    Give the product a distinct brand without forking a component library

    Pick one of the seven themes and override its CSS custom properties; existing Tailwind classes still apply. Budget time for upgrades while the project is in beta.

  • A platform engineer standardising UI across several React 19 apps

    Keep agents and people on the same component conventions across repos

    Install the CLI globally and in each project; each repo answers from its own pinned version, and astryx doctor flags projects whose agent docs or integrations have drifted.

Before you commit

Setup
npm install @astryxdesign/core, a theme package and @stylexjs/stylex, plus @astryxdesign/cli as a dev dependency; add a few CSS imports and a theme provider. Guides cover Next.js, Vite, Tailwind and CDN use. React 19+ and Node 22+ for contributors.
Integrations
Typed React components; CLI with search, component, hook, docs, template, theme, swizzle, upgrade and doctor commands, all with --json output; codemods for upgrades, including refreshing shadcn-copied components; integration packages can add components and docs.
Data and privacy
A client-side library with no hosted service. The CLI reads its docs from the installed package and notes when a newer version exists; no telemetry is described in the README. MIT licence with no commercial limits.
Cost at scale
Free at any scale. The cost is engineering time: upgrades during the 0.x beta and ownership of any component you swizzle.
Limits
Beta, with releases several times a week and 679 open issues and pull requests. Charts are canary-only; the experimental lab package is not published. React 19 or later only.

What’s good

  • 150+ accessible components with templates for whole pages
  • CLI answers in typed JSON from the installed version
  • Pre-built CSS; override with Tailwind or plain CSS
  • Seven themes, set through CSS custom properties
  • MIT licence, no paid tier

What’s not

  • Still beta at version 0.7.x; frequent releases
  • Requires React 19 or later
  • Charts only on a canary tag
  • Swizzled components become yours to maintain

Best for

React teams starting a new app or internal tool who expect coding agents to write much of the front end and want them working from a documented component set.

Astryx alternatives

Astryx: common questions

Is Astryx worth it?
A mature component library with an unusually agent-friendly CLI, worth adopting for a new React 19 app, though its beta label and 0.x version mean breaking changes are still part of the deal. We rate it 4.0 out of 5.
How much does Astryx cost?
Free under the MIT licence; no paid tier.
What are the downsides of Astryx?
Still beta at version 0.7.x; frequent releases; requires React 19 or later; charts only on a canary tag; swizzled components become yours to maintain.
Who is Astryx best for?
React teams starting a new app or internal tool who expect coding agents to write much of the front end and want them working from a documented component set.
How much does Astryx cost for a team or in production?
Free at any scale. The cost is engineering time: upgrades during the 0.x beta and ownership of any component you swizzle.
Is Astryx safe for company data?
A client-side library with no hosted service. The CLI reads its docs from the installed package and notes when a newer version exists; no telemetry is described in the README. MIT licence with no commercial limits.
What are the best Astryx alternatives?
The closest alternatives we have reviewed are Impeccable, Hallmark and OpenDesign.

Answers checked Nov 11, 2026.

Make Astryx? Show this rating on your siteAstryx rated 4.0 out of 5 on ReviewRamble