A design catalog outdraws the DESIGN.md spec it's built on

DESIGN.md's companion catalog already outpaces the spec it's built on. VoltAgent's awesome-design-md counts 105,691 GitHub stars and 12,087 forks, against 26,805 for the spec itself, nearly 4x as many. The catalog's pitch is that teams skip original design work entirely: drop in a DESIGN.md file reverse-engineered from a known brand, and an agent generates a matching UI.

The spec underneath is more particular than the pitch suggests. A DESIGN.md file carries YAML front matter for color, typography, spacing, radius and component tokens, plus markdown sections explaining the reasoning behind them. It's released under Apache-2.0 and still labeled alpha.

The @google/design.md CLI is built for engineers, not marketers. It lints a DESIGN.md file against 11 rules, including WCAG contrast checks, and returns structured JSON findings. It also diffs tokens between file versions and exports to Tailwind v3/v4 JSON, plain CSS, or the W3C Design Token Format.

I came up as a designer before I was an engineer. The lint rules are the half of this I'd actually use: a machine-checkable way to catch a contrast failure before it ships. The reverse-engineered brand catalog is the half I'd worry about. As more teams drop in the same famous brand files, agent-built UIs are going to converge on the same handful of looks, not diverge.