Astryx - A customizable, agent-ready open-source design system
Astryx is Meta’s open-source design system built on React and StyleX. It includes accessible components, brand-level themes, templates, dark mode, CLI/MCP docs, and customization paths for both developers and AI agents.
Replies
Flowtica Scribe
Hi everyone!
Meta has open-sourced Astryx, the design system that has powered over 13,000 internal tools for the last 8 years. It’s out now in beta on @React and StyleX.
Astryx was built from the ground up for agents. Most design systems assume a human is reading the docs. Astryx lets agents read the same API reference through the CLI, so your agents build UI using the exact same system a human would, rather than hallucinating component props.
They also avoided the usual customization trap. You can theme it at the token level so your app doesn’t look like a Meta clone, but you can also fully eject a component’s source code if you need absolute control.
@zaczuo Congratulations on the launch. This looks pretty cool.
@zaczuo the thing that'd actually save me time is the agent reading the same api ref i do. right now claude code building an angular component against our own design system just guesses props — invents a variant that doesn't exist — and it surfaces in review, not at build. one ref both sides pull from kills that whole class of bug.
The tagline points to digital connection, but the topic hints cover a pretty wide span: Design Tools, User Experience, AI Workflow Automation, Marketing & Sales, and AI Agents. Is Meta meant to start with one specific user group first, like designers, community builders, or product teams, or is the idea to connect those workflows from day one?
Agent-readable design-system APIs are a practical shift. The key is making the allowed component contracts easier for agents to follow than inventing their own props; otherwise the system still depends on a human cleaning up drift after the fact.
token-level theming plus a full source eject covers the exact case that always bites me. every design system i've built on eventually hits one component the tokens can't express, and then it's fork-the-whole-thing or wrap it in hack divs. 90% through tokens, own the source for the last 10% — that's the escape valve i want.
the agent-reads-the-same-reference idea is the right instinct. what happens when astryx itself ships a breaking change to a component's props, does the CLI reference update live so the agent always sees current state, or is there a window where an agent working from a slightly stale local copy of the docs confidently generates code against an api that no longer exists