Awesome DESIGN.md Ships 73 Brands' Design Systems as Agent Files. One Unlisted Entry Tells on the Whole Repo.

A 113,000-star repo hands your coding agent Stripe's or Airbnb's exact visual language in a plain-text file. The interesting part is the one brand it renamed and hid.

Seventy-three companies' design systems, reduced to markdown, sitting in a public repo that a coding agent can read in one gulp. Copy the file into your project root, tell the agent "build me a page that looks like this," and you get UI in Airbnb's coral or Vercel's monochrome without ever opening Figma.

VoltAgent/awesome-design-md did 113,535 stars and 12,825 forks in five months. It was created on March 31, 2026. It is MIT licensed. It is, mechanically, one of the fastest ways to make an AI-generated page stop looking AI-generated.

It also contains one folder that its own maintainers apparently thought twice about, and that folder is the most informative file in the repository.

What the format is and why it works

DESIGN.md is a convention that came out of Google Stitch: a plain-text design system document that an agent reads to generate consistent UI. It sits beside AGENTS.md in a project, and the repo's own table frames the split cleanly. AGENTS.md tells coding agents how to build the project. DESIGN.md tells them how the project should look and feel.

The reason this works is boring and correct. Coding agents are excellent at following an explicit token table and terrible at inferring visual intent from adjectives. Tell an agent to make a page "modern and clean" and you get the same slightly gray SaaS page every time. Hand it primary: "#4a154b", a named font stack, a spacing scale, and a set of component rules, and the output snaps into a coherent identity because there is nothing left to guess.

The files are substantial. The Airbnb entry runs a little over 30 KB and carries a "Known Gaps" section admitting what "was not visible in the captured surfaces," which is a level of intellectual honesty most design documentation never reaches. Files are scoped to specific pages, and some list them: the Slack file names its sources as home, /features/channels, /pricing, and /contact-sales.

The repo says where the content comes from: "This repo provides ready-to-use DESIGN.md files extracted from real websites." What it never says is how. No tool is named, no model, no pipeline, no statement of whether extraction was automated. If you are evaluating this repo for a client project, that gap matters more than it looks.

The entry that gives the game away

The README advertises 73 files. Its badge says 73, and I counted 73 entries across the ten category sections. The design-md/ directory contains 74 folders.

The extra one is slack. It is not listed in the README anywhere. Search the file for "slack" or "slacc," case-insensitive, and you get zero hits. The collection is alphabetized within each category, and under Productivity & SaaS the entries run Cal.com, Intercom, Linear, Mintlify, Notion, Resend, Zapier. Slack would sort between Resend and Zapier. It is simply gone.

Open the file itself and it gets stranger. The front matter reads:

name: Slacc-Inspired-design-analysis
description: An inspired interpretation of Slacc's design language...

Slacc. With two c's. The body keeps it up: "Slacc's design language centers on a deep aubergine primary." The string "Slack" with a k appears nowhere in the file.

Except the values are Slack's. The primary color is #4a154b, Slack's actual aubergine. The font stacks are Salesforce-Avant-Garde and Salesforce-Sans, the proprietary typefaces of Slack's parent company. The source pages are Slack's URL paths.

Now compare it to the Airbnb file, which sits in the same repo, is listed in the README, and whose front matter reads simply name: Airbnb-design-analysis. No fictional spelling. No "inspired interpretation" framing. Airbnb by name, throughout.

Someone made a decision about Slack that they did not make about the other 73. They renamed the brand, reframed the document as an interpretation rather than an analysis, and pulled it from the index while leaving the file on disk. That is not a typo. That is a risk assessment, executed once, on one entry, and never explained.

The disclaimer, in full

Here is the entire legal posture of a repository distributing 73 companies' visual identities:

This repository is a curated collection of design system documents extracted from public websites. All DESIGN.md files are provided "as is" without warranty. The extracted design tokens represent publicly visible CSS values. We do not claim ownership of any site's visual identity. These documents exist to help AI agents generate consistent UI.

That is it. The word "trademark" does not appear in the README. Neither does "permission." Neither does "consent." No brand is described as having authorized inclusion, no attribution is requested of users, and there is no takedown policy.

"We do not claim ownership" is an ownership disclaimer. It is not a statement about what you are allowed to build with the file, which is the only question a reader actually has.

I am not a lawyer and this is not legal advice, so take the following as the shape of the question rather than an answer. Individual design tokens are weak candidates for protection. A hex code is a fact about a stylesheet. A spacing scale is arithmetic. Reading a public site's CSS is not the interesting part.

The interesting part is what the format is designed to do, which is reproduce a total look and feel on demand. The README's own pitch is "build me a page that looks like this." A page that looks like Stripe's, shipped commercially in a space where a customer might reasonably wonder about the relationship, is a different conversation from a hex code. And the repo's own handling of Slack suggests its maintainers have had some version of that conversation with themselves.

Put this into practice

None of that means skip the repo. It means use it for the thing it is unambiguously good at.

Start by reading two files, not by copying one. Open the Airbnb DESIGN.md and one other from a different category. You are learning the format, not shopping for an identity. Twenty minutes with two files teaches you what a token table, a component rules section, and a Known Gaps section look like when they are written well.

Then write your own. Point an agent at your own site or your client's, with permission you already have, and produce a DESIGN.md in the same structure. This is the whole value with none of the exposure. You get the deterministic-output benefit, and the identity being reproduced is one you are entitled to reproduce. Every file in the repo is a worked example of how to do it.

Use borrowed files for structure, not for identity. Lifting Vercel's spacing scale and elevation model into your own palette is ordinary craft. Shipping a commercial product in a named brand's exact color and typeface because a file made it one command away is where you should stop and ask a real lawyer.

Verify anything you take against the live site. The last commit to this repo landed July 31, 2026, roughly a month before I wrote this. The repo's updated_at timestamp says September 2, but that is star churn, not code. Sites redesign. A stale token table produces confidently wrong UI, which is worse than no UI.

Do not expect the repo to grow the way you want. CONTRIBUTING.md says it plainly: "We cannot accept DESIGN.md pull requests to maintain the quality of the existing collection." New brands cannot be contributed. They route to a paid request form instead.

What the README gets wrong about itself

A few things do not survive checking, and they are the kind of thing that should adjust your trust in the rest.

The README says each site includes three files: DESIGN.md, preview.html, and preview-dark.html. The Airbnb folder contains a DESIGN.md and a 209-byte README.md. The preview files 404. CONTRIBUTING.md still instructs contributors to update preview files that are not there.

The README's format table lists nine sections it says every file follows, including "Do's and Don'ts" and an "Agent Prompt Guide." The Airbnb file has neither. The Slack file has the first but ends with an "Iteration Guide" instead of the second. The format is a goal, not a guarantee, so read the file you are about to depend on rather than the table describing it.

Every one of the 73 entries links to getdesign.md/<brand>/design-md rather than to the file in the repository you are already looking at. Each brand folder's own README is a redirect: "Design system details have been moved to: https://getdesign.md/airbnb/design-md." The repo also carries LaunchKit and EveryFeed promotions and a sponsorship CTA claiming the project is "Ranked #150 globally on GitHub," which I could not verify anywhere.

So the honest description is that this is an excellent free artifact and a funnel at the same time. Both things are true, neither is disqualifying, and knowing it changes how you read the README's claims about itself.

The part worth taking seriously

Machine-readable design specs are going to be normal within a year. The format is good, the mechanism is sound, and the productivity gain when an agent stops guessing at your visual intent is immediate and obvious.

The open question is whether "publicly visible CSS values" stays a sufficient answer once these files are the standard input to commercial UI generation at volume. Nobody has litigated it. There is no norm yet, no attribution convention, no opt-out registry.

What we do have is one repository with 113,000 stars, a four-sentence disclaimer, and a single folder where somebody changed a k to a c and pulled the entry from the index without a word about why. Whatever they were worried about, they did not write it down. Read the collection, learn the format, then write your own file for a brand you actually own.

Sources: VoltAgent/awesome-design-md on GitHub, with the README, LICENSE, CONTRIBUTING.md, and the Airbnb and Slack DESIGN.md files read cache-busted from raw.githubusercontent.com on September 2, 2026; star, fork, and date figures from the GitHub REST API for the repository the same day; the Stitch DESIGN.md specification.