Astryx

Meta has spent eight years quietly building Astryx into the design system that runs across more than 13,000 internal apps, and now it's handing the whole thing over as open source. That's not a small gesture. Design systems are usually the kind of thing companies guard closely because they encode years of accumulated UI decisions, accessibility fixes, and hard-won conventions. Astryx ships with over 150 accessible React components, theming support, dark mode, ready-made templates, and a CLI, all built on StyleX rather than a framework like Tailwind or CSS Modules.

What's actually interesting here isn't the component count, it's the philosophy behind how those components are exposed. Astryx avoids the usual trap of locking functionality behind a tidy but restrictive top-level API. Instead, the pieces you'd normally have to fork or hack around are exported directly, and if you need to go further, a "swizzle" command ejects a component's full source straight into your codebase. Theming works through CSS custom property overrides rather than wrapping or forking components, so a design team can reskin the whole thing without touching source code. And because Astryx authors its styles in StyleX but only exposes plain classNames to consumers, you can layer Tailwind or vanilla CSS on top without any conflict.

The more unusual pitch, though, is the explicit design-for-AI angle. Meta says the API, documentation, and CLI were built so that a human developer and an AI coding assistant work from identical references and produce the same output. That's a deliberate response to how software actually gets written now, with agents doing meaningful chunks of implementation work alongside engineers. Meta claims every change that made the system easier for AI to use also made it easier for people, which is a convenient claim but not an implausible one — clearer conventions tend to help both.

Getting started doesn't require much ceremony. You install the core package plus one of seven themes (options range from neutral to, oddly, "y2k" and "gothic"), add the CLI, and you're working with typed components and pre-built CSS with no PostCSS or Babel configuration required. A few packages, like the Vega chart wrapper and a broader charts library, are still canary-only with no stable release yet, so this isn't a fully finished product. But the core system, license included as MIT, is ready for outside contributors, complete with its own rubrics for API conventions and component lifecycle management.