HeyDesigner · 11 Jun 2026
Using Uber's uSpec as a case study, the piece argues that design systems are now consumed by AI agents as much as by human engineers — and that the quality of agent-generated code is determined not by documentation written for humans but by how precisely contracts are encoded in token naming, prop types, and component composition rules. A system with semantic token naming (e.g. `color-feedback-critical` vs. `blue-600`) and typed prop constraints generates accurate agent output; one relying on Storybook prose generates plausible-but-wrong output that compiles.
Industry lens
Product teams in travel that are accelerating front-end velocity with agentic coding tools are doing so on the assumption that their component libraries are machine-readable; teams whose systems were built for human implementation will not discover the gap until agent-generated components start diverging from design intent in production.
“Your system is already making promises. The question is whether those promises are written down clearly enough that something other than you can read them and get the right answer. The difference shows up in the output. It always has, and it's just easier to see now.”
— HeyDesigner
