What happened

Nielsen Norman Group published a piece on July 24, by Tony Alicea, arguing that UX work should stop terminating in human-only artifacts — personas, journey maps, research reports — and start producing machine-readable context that AI tools read when they generate design. The imagined end state is a "UX.md" file: research findings, interaction standards, terminology glossaries, and models of who your users are, all sitting where AI tools can consume them.

The anchor holding the idea up is real. Google Labs open-sourced DESIGN.md in April 2026 — a file that lives alongside a product's code and pairs exact design-system values (colors, type sizes, spacing, corner radii) with plain-prose guidance explaining what each value is for and how accessibility constraints apply. A tool reading it doesn't just know your brand blue's hex code. It knows when that blue is allowed to show up.

Be clear about what exists. DESIGN.md is shipped and open source. UX.md is NN/G's thought experiment — no standard, no implementations anywhere. NN/G itself frames the piece as a direction rather than a checklist, and that's the right way to read it.

Why this matters

If you've ever let an AI tool edit your theme, you know the failure mode. The palette drifts a shade. Spacing goes soft. A button picks up a border radius nobody approved. The tool isn't broken — it's uninformed, guessing at intent from raw CSS. A tokens-plus-intent file removes the guessing.

For a BigCommerce store this is more practical than it sounds. Your theme is already code in a repo. Writing down your exact values plus one line of intent per value costs an afternoon, and it pays out every time anyone — human contractor or AI assistant — touches the theme afterward. We run our own site this way: design tokens plus intent notes live in the repo, and it's the reason AI-assisted edits don't drift the palette.

The bigger NN/G claim — that research deliverables themselves become machine context — is further out, and you can safely ignore it for now. The near-term move is narrow, cheap, and available today.

What to do about it

Write a DESIGN.md-style file for your theme

Pull the exact values from your stylesheet — hex codes, the type scale, spacing units, corner radii — and add one plain-English line per value saying what it's for. Google's open-sourced format is a working template; copy its shape instead of inventing your own.

Keep it in the repo, next to the code

A brand PDF in someone's Drive helps no tool. In the repo, the file gets versioned with the theme and lands in the context window of every AI-assisted edit automatically. Update it when the design changes, in the same commit.

Test it against a real edit

Ask an AI tool to add a promo section twice — once with the file present, once without — and diff the two outputs. If the with-file version holds your palette and spacing, you've just measured the return on an afternoon's work.