A brand’s visual identity used to live in a PDF its own design team guarded and, now and then, went to court over. Two GitHub projects suggest that era is closing. VoltAgent’s awesome-design-md, with 97,000-plus stars, and nexu-io’s open-design, with 76,000-plus, ship dozens of plain-text “DESIGN.md” files — recipes scraped from the public CSS of named brands including Apple, Stripe, Ferrari, Nike and Airbnb. Drop one into a project and any coding agent, from Claude Code to Cursor, turns out screens recognizably that brand’s, with no designer in the loop. A brand’s look is becoming a file you fork and install rather than a craft you hire and defend.
Nine headings where a brand book used to be
VoltAgent’s README pitches it plainly: “drop one into your project and let coding agents generate matching UI.” Its 73 files share the same nine headings — color palette, typography, component styles, do’s and don’ts, a prompt guide for the agent — and it’s upfront about the source: “the extracted design tokens represent publicly visible CSS values.” nexu-io’s open-design goes further, bundling 150 such files into a desktop app pitched squarely at Anthropic’s paid Claude Design product. It bills itself as “the open-source Claude Design alternative,” and shipped a release the same day this piece went out.
The collapse — from tacit craft to a swappable, openly licensed file — matters more than either project’s star count. A style guide was made once, by people paid to internalize a brand, then defended in review; a DESIGN.md is scraped, forked by strangers, and applied automatically by a tool with no stake in whether it’s faithful or just plausible. It rhymes with how shadcn/ui quietly became AI coding’s default component library: once a spec is the path of least resistance for an agent, it spreads whether or not any design team ever signed off.
A brand's look is becoming a file you fork and install rather than a craft you hire and defend.
“It’s just public CSS” is true, and not the whole story
The strongest defense is baked into the tooling: these are “publicly visible CSS values,” the kind of thing anyone can already see by right-clicking a page and choosing Inspect. Reading a stylesheet and jotting down its color codes is nothing like copying private source or leaked assets — a company that ships its palette in plaintext has, narrowly, already published it. That has real force — probably why these repositories reached tens of thousands of stars without the takedown notices obvious theft would draw. But “publicly visible” and “fair to package and redistribute at scale” aren’t the same claim. That CSS was published so a browser could draw a page, not so a competitor’s agent could spin up an unrelated product borrowing its colors and shapes wholesale. The line describes what was taken; it’s shakier as a defense of taking it this systematically, at no cost to the brands.
A second, more sympathetic case sits beside that tension. Creative Bloq’s reporting on 2026’s homogenization debate describes a default “AI design aesthetic” — the same gradients, glassy panels and centered hero layouts agents fall into when handed no real brief. A strict, opinionated DESIGN.md is one of the few things that reliably breaks the spell: an agent told exactly how Ferrari uses red makes something specific, not generic. So the same file that commodifies a brand may also be the sharpest tool against everything dissolving into sameness.
Nobody is vetting the files an agent trusts by default
What neither defense touches is provenance — where the file came from, and whether it’s even right. Anthropic’s own Claude Design, per TechCrunch’s coverage of its April 2026 launch, builds a brand’s system by “reading their codebase and design files” for that specific team, then hands back a bundle — a process with someone’s name on it and a defined scope. A community DESIGN.md has neither. It’s scraped by an anonymous contributor, merged by a maintainer who may never have touched the brand, and forkable by anyone who wants to change what it claims about, say, Nike’s motion language — with none of the review discipline these communities give their own code. That is the gap worth watching as the repositories keep growing: a brand’s defining artifact circulating with less scrutiny than the code that reads it.
