Today, I saw several times on X the case of Meta asking its employees to stay home because they were going to announce layoffs. These two statuses in particular caught my attention (Tweet 1) and (Tweet 2). posts are about Meta layoffs
It seems that with the intention of helping companies (and a little bit of fear of not being fired), we are collaborating on a project that will replace us. So the question here is not "if" but "when". And presumably, if the employees refused, someone else would be found to do it.
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.
Token level theming vs full eject is a real tradeoff. The more teams eject the less they benefit from upstream fixes. Curious how often that happens in practice.
How does the agent readable API actually compare to what Radix or shadcn already expose? Those aren't bad either.
Every big company says their design system is "built for agents" now. What's actually different here versus just having clean, well written docs that a model can parse?
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?
Hooked an agent up to our old design system last year and it kept inventing props that didn't exist. If Astryx actually solves that, it's worth trying for our team.
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.