The Problem

Teams struggle to ship design‑system components that stay consistent across both human developers and AI assistants. Existing libraries lock styling, hide internals, and require build‑time tooling that interferes with a team’s existing stack.

What This Does

Astryx delivers a fully open design system. Components are exported directly from the source tree (packages/core/src/...), so developers can import any building block without a wrapper. Styling is written with StyleX but is invisible to consumers; they can override with Tailwind, CSS modules, or plain CSS. A small CLI (packages/cli) lets users eject component source, generate tokens, or scaffold templates, keeping the toolchain minimal.

How It Is Wired

Execution starts in the docs site (apps/docsite/src/components/tokens/index.ts). That file imports tokens from packages/core/src/tokens.ts. The token module pulls JSON definitions from packages/core/src/theme/tokens.json and exposes them as key: string objects, which the component files (packages/core/src/components/*) consume.

The CLI is invoked with astryx <command>; the binary is installed from packages/cli/bin/astryx. Internally, it resolves the command via packages/cli/src/commands/*, where each command calls the relevant internal API in packages/core/src/cli/*. For example, astryx export calls packages/core/src/cli/export.ts, which writes component source to the current working directory.

The Next.js entry point for the live docs is apps/docsite/next.config.mjs; it mounts the React app at / and serves the compiled bundle. The tsconfig.json in apps/docsite ties TypeScript to the core package, ensuring type safety across the boundary.

Because the design system is pure React + StyleX, there is no webpack or Babel plugin needed. The only external side effects are file writes performed by the CLI and static asset serving by Next.js. The graph has a single dependency cycle: packages/core/src/components/* → packages/core/src/theme/*, which is intentional and documented in the README.

How To Use It

Setup

# install core, theme, and StyleX
pnpm add @astryxdesign/core @astryxdesign/theme-neutral @stylexjs/stylex
# install CLI globally for convenience
pnpm add -g @astryxdesign/cli

Configuration Add a theme provider in the root of your app (src/App.tsx in the Vite example).

import { ThemeProvider } from '@astryxdesign/core';
import neutralTheme from '@astryxdesign/theme-neutral';

<ThemeProvider theme={neutralTheme}>
  <App />
</ThemeProvider>

Running For a local dev server:

cd apps/docsite
pnpm dev

The docs site is served at http://localhost:3000.

To eject a component:

astryx export Button

The CLI writes packages/core/src/components/Button.tsx to the current folder.

Real‑World Use

A product team builds a new feature in React. They import Button from @astryxdesign/core, apply a Tailwind className, and style it with a custom CSS variable from @astryxdesign/theme-neutral. The AI assistant can generate the same code snippet by referencing the astryx API, ensuring the component behaves identically in both environments.

Code Health & Issues

  • Tests – 3450 test files across packages/* and apps/*.
  • CI – GitHub Actions workflows exist in .github/workflows/*.
  • License – MIT license in root LICENSE.
  • Structural safety – Static analysis shows no red‑flag dependencies or missing lockfiles.
  • Coverage – All components are typed in TypeScript; style usage is controlled by StyleX.

The repository currently has no reported vulnerabilities or security gaps.

The Bottom Line

Astryx offers a pragmatic, open design system that integrates cleanly with existing React stacks. Its zero‑plugin, token‑driven architecture lets developers and AI assistants share the same component source, reducing friction when scaling design work. Suitable for teams that need consistent UI primitives without locking into a proprietary build pipeline.