Browse DESIGN.md examples where palette systems, semantic tokens, and color logic are described as reusable design infrastructure.
What To Compare
Study how these systems document surfaces, accents, text contrast, semantic states, and token naming so color decisions remain durable across implementation.
What To Compare
Pay attention to token structure, contrast strategy, accent restraint, light/dark mode logic, and whether color intent is obvious from the system itself.
Design Analysis
--- version: alpha name: Editorial Agent Mail description: A white email-infrastructure language with oversized Cooper-style serif headlines, monospaced controls, violet CTAs, measurement-like pricing controls, and quiet... --- version: alpha name: Desktop Ops...
AutoSend
Home
--- version: alpha name: Editorial Agent Mail description: A white email-infrastructure language with oversized Cooper-style serif headlines, monospaced controls, violet CTAs, measurement-like pricing controls, and quiet...
Open exampleToDesktop
Home
--- version: alpha name: Desktop Ops Nebula description: A desktop release-platform design language with dark nebula hero stages, circuit-line framing, blue action buttons, translucent nav, light documentation shells, an...
Open exampleSaugat
Home
--- version: alpha name: Gridded Portfolio Ledger description: A minimal designer portfolio language with white ledger grids, black pill navigation, small color filter tags, large product screenshots, paper-note details,...
Open exampleStudy how these systems document surfaces, accents, text contrast, semantic states, and token naming so color decisions remain durable across implementation.
A focused collection makes it easier to compare how teams describe one system concern consistently across many examples instead of mixing unrelated signals on a single page.
