// the take
A library of 200 reverse-engineered DESIGN.md files — one per popular app (Spotify, Uber, Venmo, etc.) — meant to be dropped next to an AI coding agent's context so it reproduces that app's look (colors, type ramps, component states, motion, haptics) instead of guessing. Each app ships four variants: framework-neutral, SwiftUI, Expo/RN, and Jetpack Compose. Useful for anyone prototyping a UI that needs to feel like a specific real app, especially if they're leaning on Claude/Cursor/Codex to generate the screens.
The spec format is consistent and genuinely detailed — exact hex values, light/dark variants, SF Symbols/Material tokens, Dynamic Type behavior, haptics — not vague mood-board language. 200 apps × 4 flavors is real breadth, and it's just markdown: no build step, no JSON schema, no plugin, you literally copy a file into your repo. The category organization (social, finance, travel, etc.) with a live rendered gallery makes browsing/picking the right one fast.
These are reverse-engineered from observation, not pulled from official design tokens, so accuracy per app is unverifiable and there's no changelog or version pinning — if Spotify reskins, you have no way to know whether the file in your checkout reflects the old or new look. Keeping 800 files (200 apps × 4 flavors) in sync with apps that redesign regularly is a maintenance load that doesn't scale to one maintainer, and there's no tooling/tests to catch drift. Reproducing exact brand palettes and UI systems for trademarked apps sits in a legal gray area the disclaimer doesn't really resolve — a takedown request from any of these 200 companies is plausible. Worth noting this repo is also a funnel for spectr.to, the commercial gallery/generator product; the free files are the loss-leader, not necessarily the main thing being maintained long-term.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →