Browse DESIGN.md examples that make component rules explicit through buttons, navigation, cards, variants, and state definitions.
What To Review
Compare how teams define reusable components, state logic, emphasis levels, and naming conventions so implementation becomes less ambiguous.
What To Compare
Look for state coverage, component naming clarity, variant strategy, interaction rules, and whether the system is strong enough to support repeated UI work without ad hoc decisions.
Design Analysis
--- version: "alpha" name: "Monument Mono Event Poster" description: "A typographic event-poster system built from white space, black monument type, mono navigation, and sharp vermilion interrupts." colors: primary: " 0A... --- version: alpha name: "Clinical M...
Laracon 2026
Home
--- version: "alpha" name: "Monument Mono Event Poster" description: "A typographic event-poster system built from white space, black monument type, mono navigation, and sharp vermilion interrupts." colors: primary: " 0A...
Open exampleCoding Bio
Home
--- version: alpha name: "Clinical Modular Lattice" description: "Scientific marketing system with navy type, white space, modular geometry, and yellow signal accents." colors: primary: " 010A21" secondary: " 6D7483" ter...
Analogue Agency
Home
--- version: alpha name: Editorial Contrast Stage description: A portfolio language built on giant grotesk type, floating pill navigation, pale-to-black chapter contrast, and a subtle global cursor follower. colors: prim...
Open exampleCompare how teams define reusable components, state logic, emphasis levels, and naming conventions so implementation becomes less ambiguous.
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.
