Choose a design system for your app

Context & limitations

Start by separating the two things, because they are both VoltAgent's and that is precisely why the numbers blur. One is a GitHub repository — awesome-design-md, MIT licensed, 73 DESIGN.md files you clone or download, no account, nothing to pay, now or later. The other is getdesign.md, a website from the same team, and it is a catalogue rather than a download: 550+ design systems you browse brand by brand, each with a short characterisation of the look and a link to the full analysis, with paid services sitting alongside it. The caption's 2,000+ belongs to neither. That distinction is practical rather than pedantic — watch the video, go to the free repo, search for your industry's best-known site, and there is a fair chance it isn't among the 73. Not because anyone misrepresented anything, but because a curated repo and a much larger catalogue got flattened into a single figure. Work out which door you're standing at before you plan around a brand being behind it.

Then "free", which is true in the way these things are usually true. The GitHub collection is MIT and genuinely, permanently free: take all 73, use them commercially, no account. Around it sits an ordinary business — an analysis of a site you name, a production starter kit, a pass for the wider catalogue. None of that is concealed and none of it makes the repo less free. It is the familiar difference between a free repo and a free project, and the moment it stops being academic is the moment the brand you actually wanted isn't one of the 73.

The omission is the most interesting part. DESIGN.md is not one clever person's convention — it's a format specification from Google Labs, open-sourced out of Stitch under Apache-2.0, with a published schema and a CLI you can run today. That changes what this is. You are not dependent on anyone's collection: because the format is public and documented, several independent tools already generate spec-valid files from any live site, which means the highest-value move isn't borrowing Ferrari's design language at all — it's pointing one of them at your own product, or at the one competitor whose site you actually admire, and getting a file nobody had to publish for you. The spec is in alpha and still moving, so pin what you generate rather than assuming last month's file still lints clean.

Which leaves the claim underneath all of it: that a billion-dollar design language transfers to your project. Mostly it doesn't, and the reason is fit rather than quality. Ferrari's system is engineered for a full-bleed hero, enormous type and nine words of copy; drop it onto a product with a settings page, a data table and an empty state and you will spend your afternoon fighting it. The systems that transfer well are the ones built for the same job you're doing — Stripe, Linear, Vercel, Notion are documentation-and-dashboard systems, which is why they keep working on other people's dashboards. The fonts are the other quiet catch: brand typefaces are proprietary, so the files name Google Fonts substitutes, and "the exact fonts" stops being exact right there. The honest version of why this works at all is less glamorous than the pitch and more useful — what kills generic AI output isn't borrowed prestige, it's having any committed, specific constraint written in a file the agent re-reads on every page. A file you generated from your own product does that just as well as Apple's, and it fits.