Real design systems become AI UI context

v0's Design Systems 2.0 announcement points to a shift from prompt-only UI generation toward outputs grounded in a team's real components, tokens, docs, starters, and source constraints. Why it matters: AI UI tools become more production-relevant when they can use the actual design system as executable context. The differentiator is no longer just visual taste; it is whether generated screens respect component APIs, tokens, dark mode, brand patterns, and starter app conventions.

Try this: Test an AI UI tool against a real design system, not a blank prompt: import the system, ask for a dense product screen, then audit component usage, token fidelity, accessibility patterns, dark-mode behavior, and how much code would need rewriting before merge.