Design systems are no longer only for human designers and engineers — increasingly, automated agents and developer tools need predictable, machine-readable APIs and docs. Astryx treats that as a first-class requirement: the system’s APIs, documentation, and CLI are designed so a human and an AI assistant can work from the same reference without extra glue, enabling reproducible component composition and programmatic scaffolding.
What Sets It Apart
- Open internals: components export composable building blocks and support "swizzle" to eject full source into your repo — so automation can modify implementation-level code when needed. This makes programmatic transformations and codemods straightforward.
- No styling lock-in: styles are authored with StyleX but consumers override with className, CSS variables, Tailwind, or plain CSS. For agents that generate UI, this reduces fragility because generated output doesn’t depend on a proprietary runtime.
- Theme-by-CSS-vars: themes are collections of CSS custom property overrides, so visual customization is a matter of token substitution rather than wrapping components — simpler for both designers and automated theming pipelines.
- Agent-friendly CLI & JSON API: the CLI exposes typed JSON envelopes and a machine-oriented manifest, letting tools and agents query component docs, templates, and codemods programmatically.
Who It's For & Tradeoffs
Great fit if your team needs consistent, predictable UI primitives that can be composed by humans and automated agents alike — design systems teams, product teams with automation workflows, or projects that want a typed React component surface plus a CLI for programmatic integration. Look elsewhere if you need a non-React-first solution, require fully stabilized/published npm packages for every experimental subpackage (some lab packages are internal/beta), or prefer a different styling runtime — Astryx currently centers StyleX internally and is labeled Beta, which implies some APIs and packages may change.
