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.
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.
Does the CLI reference update automatically when components change?
The "eject the component" option sounds great until you're the one maintaining a forked mess later.
No mention of Vue or Svelte support here that's a gap for some teams.
8 yrs of internal use means it's battle tested, but packaging something for public use is a different job entirely.