Design System by Prompt

Figma's stock dropped 8.8% in a single day. The reason: Google Stitch announced it can now create a complete design system from a single prompt.

Colors, typography, spacing, components. Everything that teams spend weeks building and documenting, generated in minutes and exported in a text file readable by any AI agent. Google calls this format DESIGN.md: a file that any tool on the market can read, interpret, and apply.

The market reacted as if design systems had been commoditized. In that reaction lies a confession: for years, we treated the artifact as if it were the value.

DESIGN.md can export the rules. It cannot export the reasoning behind them. It does not capture the judgment that determined what the system should not include, nor the perception of when a rule needs to change because the product grew in a direction the system never anticipated.

Building the artifact was always the most tangible step. The harder part was something else: knowing which rules are worth creating, when to break them, and when the entire system needs to be revisited.

That does not change with a prompt.

But there is a real shift that Stitch introduced that most people are ignoring in the debate about Figma's stock drop. Design systems that are not readable by AI agents will become legacy. Not because they are worse, but because they fall outside the flow. The market is reorganizing around systems that machines can operate, and libraries locked inside proprietary tools do not fit that circuit.

Tools become obsolete. Judgment does not.

What Stitch revealed, unintentionally, is that the part of a design system that can be automated was always the least valuable. It was necessary, but it was not what differentiated.

What differentiates is what cannot be exported.

---

Source: https://blog.google/innovation-and-ai/models-and-research/google-labs/stitch-ai-ui-design/