# Astryx

> Source: https://aiwiki.ai/wiki/astryx
> Updated: 2026-11-17
> Categories: Developer Tools, Software Development
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) - attribute to "AI Wiki (aiwiki.ai)"
> Cite as: AI Wiki. "Astryx." aiwiki.ai, 17 Nov 2026. https://aiwiki.ai/wiki/astryx
> From AI Wiki (https://aiwiki.ai), the free encyclopedia of artificial intelligence. Reuse freely with attribution.

**Astryx** is an open-source design system from Meta for building web interfaces with [React](https://aiwiki.ai/wiki/react). It provides UI components, themes, page templates and development tools that people and [AI coding agents](https://aiwiki.ai/wiki/ai_coding_agent) can use from the same documentation. Meta introduced its public beta on June 18, 2026. It is software for constructing interfaces, rather than an AI model or a hosted application builder.[1][2]

The project is distributed under the MIT license. Its public implementation uses React 19 or later and StyleX, with typed component interfaces and precompiled CSS. Developers can use the compiled packages without adding a StyleX compiler to their build.[2][3][4]

## Origins and scope

Astryx grew out of Meta's shared UI system for internal tools. The team describes the public project as a rebuild on an open-source stack, retaining conventions and experience from eight years of internal development. Meta reports that the predecessor system powered more than 13,000 internal products. That figure describes Meta's internal usage, rather than the number of independent adopters of the public package.[5]

The system combines reusable controls with conventions for layout, styling and composition. Its documentation includes components, hooks, templates, design tokens, example applications and migration guidance. The public project remains labeled beta, even though its origins are in an established internal system.[2][5]

## Packages and customization

| Part | Purpose |
| --- | --- |
| `@astryxdesign/core` | React components, theme infrastructure and utilities |
| `@astryxdesign/cli` | Documentation lookup, templates, project initialization, themes and migration tools |
| `@astryxdesign/build` | Build tooling for applications compiling StyleX source |
| `@astryxdesign/theme-*` | Packaged themes that define the interface's visual appearance |

These are separate packages within the same repository. The core library supplies [TypeScript](https://aiwiki.ai/wiki/typescript) interfaces. A developer can begin with prebuilt CSS, use `className` overrides with ordinary CSS or Tailwind, or compile from the TypeScript and StyleX source for more control.[2][3][5]

Astryx separates component behavior from theme appearance. The documented customization path progresses from changing theme tokens to applying styles and, when necessary, copying a component's source into the application with the `swizzle` command. Copying source gives the application responsibility for that local implementation.[5][6]

### Themes and color modes

The bundled theme families are Neutral, Butter, Chocolate, Gothic, Matcha, Stone and Y2K. Themes can specify colors, typography, spacing, motion and component-level overrides. The `Theme` provider supports system preference, light mode and dark mode; a theme may also be designed for a single color mode.[7]

The current theme workflow distinguishes adding a package theme from ejecting its source. `theme add` records the theme and generates the application imports for its built module and CSS. `theme eject` creates an independent local source fork. Package updates continue to reach an added package theme, while an ejected theme is maintained locally.[7]

For applications using server rendering, the documentation recommends built theme CSS. Runtime theme overrides are injected during hydration and can flash before they apply; precompiled overrides are present in the CSS used for the initial render.[7]

## Installation and development workflow

Astryx requires both `react` and `react-dom` version 19 or later. The getting-started guide installs the core package, its `@stylexjs/stylex` peer dependency, a theme and the CLI. It then initializes project guidance with `npx @astryxdesign/cli init`.[8]

The package's default distribution includes stylesheets for the reset, component styles and theme values. Their cascade order matters. Applications with existing global CSS or Tailwind must also account for unlayered styles and CSS layer ordering. The project supplies examples for [Next.js](https://aiwiki.ai/wiki/nextjs), Next.js with StyleX, Next.js with Tailwind, and Vite with Tailwind.[3][8]

The scoped package name matters when invoking the CLI through `npx`: the documentation warns that the unscoped package name `astryx` can resolve to unrelated software before the Astryx CLI is installed. A project dependency and lockfile identify the version used by the team and CI. A global CLI installation delegates to the project's own CLI when available, rather than forcing its global version onto the project.[6][8]

## Working with AI coding agents

Astryx's agent support centers on supplying the installed library's actual APIs. The initialization command can generate a component index, behavioral rules and CLI guidance in project instruction files. The working-with-AI guide describes support for tool-specific files, including `AGENTS.md`, `CLAUDE.md` and Cursor rules, with upgrade tooling to refresh managed instructions after dependency changes.[9]

The recommended sequence is to look up an appropriate page template, scaffold it, and read each component's props and examples before writing the interface. Documentation generation is a way to give an agent context; it does not establish that all code the agent produces is correct.[9]

| CLI lookup | Information returned |
| --- | --- |
| `search` | Ranked matches across components, hooks, documentation, templates and themes |
| `component` | Component APIs and examples |
| `build` | A starting template and related building blocks for a requested page |
| `template` | Template listings or source for scaffolding |
| `docs` | Reference material and workflow guides |
| `manifest` | Machine-readable command capabilities |

The CLI also offers typed JSON responses for automation. Its command manifest describes arguments, options and response types. This gives an agent a structured interface in addition to readable terminal output.[6]

### Model Context Protocol

Astryx supports the [Model Context Protocol](https://aiwiki.ai/wiki/model_context_protocol) for AI tools that use MCP instead of shell commands. The local server starts through `npx @astryxdesign/cli mcp` and communicates over standard input and output. It exposes the CLI's JSON-capable commands as tools and answers using the project's version, theme and integrations.[9][10]

The hosted endpoint, `https://astryx.atmeta.com/mcp`, serves documentation for the latest published release. Its documentation-only mode excludes inputs naming local folders, output files or packages to read. It therefore differs from the local project server in both available operations and version context. The current official guide recommends direct CLI use when an agent can run commands.[9][10]

### Integration with v0

On November 14, 2026, the Astryx team announced availability in v0 as a design-system skill. Selecting Astryx supplies its guidance, components, examples and templates as context while v0 builds a project. This integration is separate from Astryx's June public beta and from its local CLI and MCP interfaces.[11]

## Accessibility and browser support

Astryx maintains accessibility requirements for component development, including accessible names, ARIA roles and states, keyboard behavior, focus management, announcements, reduced motion and contrast. Its contributor checklist points to additional requirements for claims that depend on real assistive-technology and browser behavior. These are development and review requirements, rather than a blanket certification of every application built with Astryx.[12]

Browser support depends partly on modern platform features: the Popover API, CSS anchor positioning and CSS `light-dark()`. The official support guide distinguishes full rendering fidelity from functional use with degraded overlay placement.[13]

| Support tier | Documented behavior |
| --- | --- |
| Tier 1 | Full fidelity, including positioning menus and other layered surfaces relative to their trigger |
| Tier 2 | Controls remain usable, but layered surfaces may lack correct anchor positioning |
| Below Tier 2 | Best effort, with possible positioning and theme-color degradation |

Astryx officially supports the first two tiers. It does not provide a `light-dark()` fallback for older browsers. Applications serving browsers without anchor positioning must choose whether to add a polyfill, provide their own positioning fallback or accept the degraded positioning.[13]

## Evaluation and limits

The team publishes an agent-evaluation approach it calls "vibe tests." It describes running the same prompt battery across Astryx, Astryx with Tailwind, a shadcn/Tailwind baseline and raw HTML, with separate judging of generated output. The measured dimensions include correctness, accessibility, code quality, efficiency and maintainability; rendered design evaluation was described as work in progress.[14]

These are project-maintained evaluations, not independent evidence that Astryx always produces better interfaces. The team's own account reports variation between runs, including cases where agents invented imports or props and the baseline won. Its tests inform changes to documentation and tooling rather than guaranteeing the outcome of a particular application.[14]

The beta designation and package status also matter when selecting dependencies. The repository identifies `@astryxdesign/lab` as internal and unpublished to npm, while its Vega wrapper and chart packages are available under the `canary` distribution tag rather than a stable release.[2]

## References

1. Astryx team. ["Introducing Astryx by Meta: an open source design system built for how we build now."](https://astryx.atmeta.com/blog/introducing-astryx) June 18, 2026.
2. Meta. [Astryx repository and project README.](https://github.com/meta/astryx) Accessed November 17, 2026.
3. Meta. [`@astryxdesign/core` README.](https://github.com/meta/astryx/blob/main/packages/core/README.md) Accessed November 17, 2026.
4. Meta Platforms, Inc. [Astryx MIT license.](https://github.com/meta/astryx/blob/main/LICENSE) 2026.
5. Catherine and Cindy. ["How Astryx works."](https://astryx.atmeta.com/blog/how-astryx-works) June 29, 2026.
6. Meta. [`@astryxdesign/cli` README.](https://github.com/meta/astryx/blob/main/packages/cli/README.md) Accessed November 17, 2026.
7. Astryx documentation. ["Theming."](https://astryx.atmeta.com/docs/theme) Accessed November 17, 2026.
8. Astryx documentation. ["Getting Started."](https://astryx.atmeta.com/docs/getting-started) Accessed November 17, 2026.
9. Astryx documentation. ["Working with AI."](https://astryx.atmeta.com/docs/working-with-ai) Accessed November 17, 2026.
10. Meta. [`astryx mcp` command documentation source.](https://github.com/meta/astryx/blob/main/packages/cli/clients/cli/commands/mcp.doc.mjs) Accessed November 17, 2026.
11. Astryx team. ["Astryx is now available in v0."](https://astryx.atmeta.com/blog/astryx-is-now-available-in-v0) November 14, 2026.
12. Meta. ["Accessibility Checklist," Astryx project wiki.](https://github.com/meta/astryx/wiki/Accessibility-Checklist) Accessed November 17, 2026.
13. Astryx documentation. ["Browser support."](https://astryx.atmeta.com/docs/browser-support) Accessed November 17, 2026.
14. Cindy and Ernest. ["Vibe Test."](https://astryx.atmeta.com/blog/vibe-tests) July 27, 2026.

