Venture Brief · Dev Tools
Should B3 build a component library engineered so AI agents extend it without going off-brand? The demand is real. The field is already taken.
The call
The pain is real, but the wedge is already closed. AI agents genuinely do break design systems — fabricating tokens, hallucinating props, installing components that do not exist. That part of B3's thesis holds. But the exact remedy B3 pitched — a machine-readable component contract an agent can read — has already shipped from Meta (Astryx), Vercel (AI Elements), and shadcn (MCP + registries) in the last twelve months.
"Components for AI" is not defensible for a two-person team against Meta and Vercel distribution. The one sliver still open is the enforcement layer — build-time token validation, CI off-brand detection, drift linting — and even that is being circled by Spotify and Meta. Do not build a component kit. If anything here is worth pursuing, it is a narrow governance tool that plugs into shadcn, not a library that competes with it.
The landscape
Every one of these landed in roughly the last year. The market is moving fast enough that this verdict could shift within a quarter.
What we tested
Fabricated token names, spacing drift, renamed/removed props, unavailable components. Worse when the output looks on-brand but isn't.
No. Meta's Astryx, Vercel's AI Elements, and shadcn's MCP all target it directly. The concept is shipped, not open.
Weak. Pure libraries monetise poorly (Chakra). Only open-core gating works (MUI) — and that needs scale a two-person team lacks.
No. Mindshare and distribution here are owned by the largest players in the ecosystem.
Partly. shadcn's MCP does discovery/install, not brand governance. But Spotify (Encore) and Meta already target the governance half — and it only works as a layer on shadcn, not a rival.
The finding that decides it
Read this first
This isn't "an incumbent might enter." Meta, Vercel, and shadcn have already shipped the machine-readable-contract-for-agents concept. A two-person team entering here competes with all three at once.
| Who | What they shipped | Covers B3's wedge? |
|---|---|---|
| Meta Astryx · MIT · ~10.6k★ |
React/StyleX design system with a self-describing JSON manifest ("OpenAPI for the CLI") + bundled MCP server to stop agents hallucinating props. Grew inside Meta over 8 years. |
Yes — the exact concept |
| shadcn MCP + CLI 3.0 |
Official MCP server; browse/search/install by natural language; namespaced, private, authenticated registries; zero-config across Cursor, Claude Code, Copilot, Codex. |
Distribution yes · governance no |
| Vercel AI Elements |
A component library + custom registry built on shadcn's CLI, installing editable source into your codebase. |
Adjacent — components for AI apps |
| Spotify Encore via MCP |
Exposes its design system (tokens, specs, behaviour) to agents via MCP so Cursor generates on-standard, plus a gen-vs-standard testing framework. |
Yes — the governance half |
Read the terrain
If pursued at all
The component-kit version is a clear no-go. The only path worth even a discovery call is the narrow enforcement layer — and only if someone will pay for it.
Ask 5 front-end leads: would you pay for a CI check that fails a PR when an agent goes off-token / off-brand, if the components stay free on shadcn? No budget line, no venture.
Gate · ThanukaDoes Astryx / Encore let agents safely contribute new components, or only consume existing ones? The "slots-not-props contribution spec" half is less covered than consumption — verify before assuming it's room.
Gate · ThanukaOne sharp tool: token validation + CI drift check as a shadcn-registry add-on. Not a library. Not a registry. A layer.
ThenThe discipline that flagged Agrithmics on estates says the same here: do not build into Meta + Vercel + shadcn. Spend the energy on a less-crowded card.
Decision