What it is
Design.md Store is a marketplace-style library of downloadable DESIGN.md files for artificial intelligence (AI) coding tools. Its homepage metadata describes 50+ curated design systems for Claude, Cursor, and Copilot. The research found 51 packs at launch, styled after brands including Stripe, Slack, Apple, Amazon, Nike, Notion, Coinbase, GitHub, Netflix, Figma, and Uber.
It is a curated download library, not a live extractor, and not the author of the DESIGN.md specification. The site uses the Google-originated file convention, and describes its files as independent, unofficial works inspired by publicly accessible websites.
First principles
A DESIGN.md pack is a static file. Its worth depends on three facts the file cannot prove about itself: who made it, what it was made from, and when.
- Who. A pack styled after Stripe is not Stripe’s design system. Only the maker’s identity and method tell a user how close it is likely to be.
- From what. A pack can be measured from a live site, inferred by a model, or written by hand to evoke a brand. Each produces a different kind of file under the same name.
- When. A download is a snapshot. The brand it imitates keeps changing, and a static file has no way to learn that.
A linter cannot answer any of these. It checks structure, references, and contrast, not whether a pack matches the brand it is named after. That is why identity, method, and date have to be stated alongside the file.
Who is behind it
The operator is undisclosed. The researched pages showed no founder, company, GitHub organization, X account, LinkedIn account, or About-page biography. Homepage structured data lists "foundingYear":"2026" and "areaServed":"Worldwide", but identifies no person or company.
The operator’s identity is therefore UNVERIFIED / undisclosed. That matters when users are asked to place an external design file in their codebase.
Format and how an agent consumes it
The intended workflow is a literal file at the repository root:
1. Download a .md pack from the Library.
2. Rename the file to DESIGN.md (all caps) and drop it at the root of your repository — alongside package.json.
3. Reference it in your AI tool.
4. Validate with the upstream linter.The validator is Google’s upstream tool:
npx @google/design.md lint DESIGN.mdThe store says Claude Code finds the root file automatically, while Cursor needs @DESIGN.md in a prompt. It also names GitHub Copilot as a supported target. Its Claude integration documentation gives direct prompts such as “Build a settings page using the design system in DESIGN.md” and “Follow the card and button-primary tokens from DESIGN.md exactly.”
The research saw this indicative fragment from a checkout-flow spec:
# Checkout flow
## Goal
Reduce drop-off at payment step.
## States
- idle / loading / success / errorThat fragment is only indicative. A complete pack was not downloaded, so its verbatim fidelity is UNVERIFIED. No Model Context Protocol (MCP) server, command-line interface (CLI), application programming interface (API), or browser extension was found.
Pricing and access
The frequently asked questions (FAQ) page says a free tier provides 51+ curated files without a credit card; users sign in with GitHub or email to download them. The packs page listed all 51 packs as FREE. The site mentions a Pro subscription, Pro updates, and early access, but its /pricing route returned a 404 (not found) error. Exact Pro pricing is UNVERIFIED. A $12 string in minified page data was not an actual price.
What works
The product teaches a low-friction, standards-based workflow: get one file, put it where the agent can find it, and lint it. Its documentation is sensibly structured, with quickstart, integration, changelog, and comparison pages. That makes the idea easy to grasp without adopting a proprietary client.
The library also offers recognizable starting points. That helps prototype work, as long as users understand that a pack styled after a brand is not the brand’s official system.
What does not
Undisclosed ownership and a missing pricing page are a trust gap. The research could not inspect a full download, so output quality and fidelity are UNVERIFIED. Every result is also subject to the site’s own disclaimer: these are unofficial, independent works.
The interface is a static download. An agent cannot search for or fetch a fresh version programmatically. A person must pick the file and bring it into context.
What we take from it
Velofy could propose the same concise documentation shape and concrete integration prompts. It could also propose that every file carry a clear provenance label, version, source method, and named maintainer. A user should not have to guess whether a design pack is official, observed, or reconstructed.
Velofy has not shipped a pack store, package, or MCP server. The practical proposal is to build on the upstream linter while making authorship, pricing, and fidelity explicit.