Google opens DESIGN.md draft spec with CLI validator in progress

• Google published the draft DESIGN.md spec as an open format that can work across tools and platforms, according to DavidmComfort's repost of Stitch by Google.
• In 7_eito_7's overview, the pitch is a single AI-readable file for colors, typography, components, and rules, plus accessibility checks.
• 7_eito_7's feature breakdown says the current draft adds a Tokens section, has Components support in progress, and is building a CLI validator to catch spec mistakes automatically.
• Early workflow posts already treat DESIGN.md as portable input, with MengTo's demo showing DESIGN.md or HTML templates feeding Claude Design and his follow-up pointing to a library of 400-plus reusable design systems.

Google is trying to turn design intent into a file an agent can actually read. 7_eito_7's thread frames it as the end of the usual Figma, Notion, and docs sprawl, while the same thread's feature list surfaces the practical bits: tokens, upcoming components support, and a validator. The interesting twist is portability. Stitch by Google's announcement says the spec is being open-sourced for use across any tool or platform, and MengTo's workflow clip already shows people piping DESIGN.md into other generation tools.

The draft spec is aimed at a familiar handoff mess: colors in one place, component notes in another, and unwritten rules living in people's heads. 7_eito_7's before-and-after post reduces the change to one file that can hold:

• Colors
• Typography
• Components
• Rules

That structure matters because the file is meant for machines as much as humans. In 7_eito_7's example, the promise is that an agent no longer has to guess what a primary button should look like.

The useful part of the draft is not just the file name, it is the schema Google is starting to lock in. The current pieces called out in the evidence are:

• Tokens: a place to centralize design variables, per 7_eito_7's feature breakdown
• Components: support is in progress for defining UI parts, again per the same breakdown
• CLI validator: an automated checker for spec mistakes, according to 7_eito_7's post

That makes DESIGN.md feel closer to lintable infrastructure than a prettier handoff doc. The launch thread also claims accessibility can be validated automatically, which gives the validator angle more weight.

Google's announcement matters less as a Stitch feature than as a format play. The wording in the reposted Stitch by Google post says the draft spec is being open-sourced so it can be used across any tool or platform.

That lines up with one of the sharper outside reads. In illscience's commentary, the contrast is between systems that generate from an existing codebase and systems that support earlier-stage exploration. The space is already splitting into different jobs, and an open spec gives those tools something shared to point at.

The fastest evidence of adoption is not a standards debate, it is people treating DESIGN.md as a promptable asset. MengTo's post shows a simple workflow: grab a DESIGN.md file or HTML template, feed it into Claude Design, and let the tool generate the rest.

His follow-up adds two concrete details that were not in Google's launch framing:

• a library of 400-plus free design systems
• remixing into other formats such as mobile, slides, and motion design

That is a good clue about where this may spread first. A machine-readable design spec is useful on its own, but it gets more interesting once template libraries and generation tools start trading the same artifact back and forth.