Archetype
47
Code-first libraries
Open implementation is public, but language/design collateral is thinner.
Examples
Appear Here Styleguide · Aragon UI · Artsy Palette · AT UIKIT
Design systems / atlas
Generated 2026-05-02
This atlas reads the awesome-design-systems list not as a pile of UI kits, but as a map of how institutions publish components, tone, design tooling, and source code.
Listed systems
163
Public source
115
Voice & tone
70
Design kits
75
Reading
The dominant form here is not the perfect system. It is the partial publication of organizational discipline.
Most entries publish components. Fewer publish the softer layers: language guidance, design kits, or open source implementation. That asymmetry is the interesting story. It turns the list into a map of what organizations are willing to expose.
Read this as an atlas of interface governance: product companies, governments, and institutions each revealing different fractions of the same stack.
Capability archetypes
Archetype
47
Open implementation is public, but language/design collateral is thinner.
Examples
Appear Here Styleguide · Aragon UI · Artsy Palette · AT UIKIT
Archetype
29
Components, voice, kits, and source all visible.
Examples
Adobe Spectrum · Alaska Airlines · Alibaba Ant Design · Amplify UI
Archetype
26
Strong implementation plus design kits for downstream teams.
Examples
Astro UXDS · Audi UI Kit · Bento DS · Blueprint
Archetype
14
Governance and tone are public; implementation remains private.
Examples
British Gas Nucleus · Buzzvil Design System · CBRE Blocks · Hudl Design System
Archetype
13
Open code with language/governance guidance, but no public kit.
Examples
City of Boston Fleet · Gympass Yoga · Help Scout · HubSpot Canvas
Archetype
11
Visible component language, private implementation.
Examples
Enel · FutureLearn Pattern Library · GoodBarber Design System · Heroku Purple3
Archetype
10
Rich public guidance without public source repos.
Examples
Aalto University · Adjust Atlas · Atlassian Design System · BBC GEL (Global Experience Language)
Archetype
8
Design tooling is public but code is not.
Examples
Duet · ENGIE Fluid Design System · Foyer Design System · Mesh Design System
Archetype
3
Content/tone systems with no component surface.
Examples
Duolingo · Mailchimp Content Styleguide · Monzo Tone of Voice
Archetype
1
Voice and design kit published together; implementation omitted.
Examples
Finland Toolbox
Archetype
1
Visual toolkits without broader public governance.
Examples
Apple Developer Design Guidelines
Civic thread
Heuristic reading aid
A visible public-sector strand runs through the list: design systems as administrative infrastructure.
These entries show that design systems are not only startup polish or enterprise component libraries. They are also instruments for consistency, service delivery, and public trust.
Landmarks
Some systems matter because they shape discourse far beyond their own product boundaries.
Full-stack public systems
Full-stack public systems
Full-stack public systems
Closed full-service systems
Designer-ready product systems
Full-stack public systems
Full-stack public systems
Full-stack public systems
Full-stack public systems
Code-first libraries
Closed full-service systems
Code-first libraries
Voice-only standards
Kit-only references
Full index
163 source-listed systems
Artifacts
This first version stays strict about provenance: every entry here comes directly from the source README table.