The Vibeary — round-up

Best public design systems to learn from

A public design system is free documentation of decisions you would otherwise make twice, argued about, and get wrong the first time. The best ones publish not just components but the reasoning: token structure, contrast rules, motion principles, content style and how the system is governed. This shelf collects the systems worth reading end to end — government systems that take accessibility seriously, product systems with mature component APIs, and the token infrastructure that keeps them synchronised with code.

What earned a place

  • Published documentation, not just a component library
  • Accessibility rules stated explicitly and tested
  • Token architecture you can learn from
  • Actively maintained by the organisation using it

24 picks from the library

  1. 01

    .pulse

    Heartbeat Agency's open design system aimed at agency teams, with components, tokens and a lightweight governance model.

    Why it made the list: Agency-scale system sized for client work rather than a 500-person org.

    Public design systemsopen-sourceHeartbeat Agencypulse.heartbeat.ua

    .pulse preview
  2. 02

    A11Y Project Checklist

    Community-maintained WCAG checklist grouped into eighteen practical categories with plain-language, testable success criteria.

    Why it made the list: Translates WCAG legalese into checks a developer can actually run today.

    AccessibilityApache-2.0The A11Y Projecta11yproject.com

    A11Y Project Checklist preview
  3. 03

    a11y-contrast

    Command-line tool that checks colour contrast across a palette or config file, suitable for CI pipelines.

    Why it made the list: Contrast checking as a build step, not a manual browser-extension ritual.

    AccessibilityMITDarek Kay (@darekkay)github.com

    a11y-contrast preview
  4. 04

    ARIA Authoring Practices Guide

    W3C's reference implementations for thirty accessible widget patterns, each with keyboard maps, ARIA semantics and working examples.

    Why it made the list: The normative answer for every combobox and menu argument your team will have.

    AccessibilityfreeW3C Web Accessibility Initiativew3.org

    ARIA Authoring Practices Guide preview
  5. 05

    Asphalt

    GO-JEK's design system covering mobile-first components, illustration language and Indonesian-market localisation guidance.

    Why it made the list: Southeast-Asian super-app constraints produce patterns Western systems never document.

    Public design systemsopen-sourceGO-JEKasphalt.gojek.io

    Asphalt preview
  6. 06

    Astryx

    Meta's public design system documentation for its component set, foundations and interaction conventions.

    Why it made the list: Meta rarely publishes system-level design docs; this is a rare open window.

    Public design systemsfreeMeta Platformsastryx.atmeta.com

    Astryx preview
  7. 07

    Atlantis

    Jobber's design system for field-service software, with React and React Native components and scheduling-specific patterns.

    Why it made the list: Scheduling, dispatch and invoicing patterns absent from every enterprise design system.

    Public design systemsMITJobberatlantis.getjobber.com

    Atlantis preview
  8. 08

    Auro

    Alaska Airlines' design system built entirely on Lit web components with published accessibility conformance reports.

    Why it made the list: Airline-regulated accessibility work published openly, including per-component VPAT-style reports.

    Public design systemsApache-2.0Alaska Airlinesauro.alaskaair.com

    Auro preview
  9. 09

    Backpack

    Skyscanner's design system with React, iOS and Android implementations plus documented motion and RTL specifications.

    Why it made the list: One of very few systems shipping matched native iOS and Android libraries.

    Public design systemsApache-2.0Skyscannerbackpack.github.io

    Backpack preview
  10. 10

    Barista

    Dynatrace's design system for dense observability UIs: data tables, charts, filters and monitoring-specific layout patterns.

    Why it made the list: Rare public system tuned for dashboards and telemetry rather than marketing pages.

    Public design systemsApache-2.0Dynatracebarista.dynatrace.com

    Barista preview
  11. 11

    Braid

    SEEK's design system where components are constrained by design tokens so invalid layouts are literally uncompilable in TypeScript.

    Why it made the list: Type-level enforcement of design constraints — the most opinionated idea in any public system.

    Public design systemsMITSEEKseek-oss.github.io

    Braid preview
  12. 12

    Calcite

    Esri's design system for mapping applications: web components, map-specific controls and a large geospatial icon set.

    Why it made the list: Map UI controls and 1000+ geospatial icons you cannot find anywhere else.

    Public design systemsApache-2.0Esridevelopers.arcgis.com

    Calcite preview
  13. 13

    Cedar

    REI's design system with Vue components, outdoor-brand foundations and a published component lifecycle and deprecation policy.

    Why it made the list: Its governance and deprecation docs are better than its components, and rarer.

    Public design systemsMITREIrei.github.io

    Cedar preview
  14. 14

    Circuit UI

    SumUp's React design system for payments and point-of-sale interfaces, with documented money-input and currency patterns.

    Why it made the list: Payment and currency input patterns documented by a company that processes them.

    Public design systemsApache-2.0SumUpcircuit.sumup.com

    Circuit UI preview
  15. 15

    Clever Components

    Clever Cloud's open library of framework-agnostic web components for cloud-console interfaces, with per-component docs and demos.

    Why it made the list: Cloud-console primitives — logs, metrics, deploys — as reusable web components.

    Public design systemsApache-2.0Clever Cloudclever-cloud.com

    Clever Components preview
  16. 16

    Codex

    Wikimedia's design system in Vue 3, built for extreme internationalisation, RTL support and low-bandwidth contexts.

    Why it made the list: Internationalisation and RTL handled at a scale no commercial system matches.

    Public design systemsGPLWikimedia Foundationdoc.wikimedia.org

    Codex preview
  17. 17

    Default File UI

    Open design system with OKLCH scales, copyable React components, CLI registry, and an MCP server for agent installs.

    Why it made the list: Ships tokens, components, and MCP/CLI so agents can install UI pieces as source.

    Public design systemsMITdefault-filedefaultfile.com

    Default File UI preview
  18. 18

    Design System Checklist

    Open-source checklist covering planning, foundations, components, documentation and adoption stages of building a design system.

    Why it made the list: Turns a vague design-system project into a scoped, trackable backlog.

    DS process & docsopen-sourceArda Karacizmelidesignsystemchecklist.com

    Design System Checklist preview
  19. 19

    Design Systems Survey

    Sparkbox's multi-year survey of design system teams reporting on adoption, staffing, governance and measured outcomes.

    Why it made the list: Benchmark data to justify headcount — nobody else publishes numbers like this.

    DS process & docsfreeSparkboxdesignsystemssurvey.seesparkbox.com

    Design Systems Survey preview
  20. 20

    design.systems

    Community hub linking design system Slack groups, newsletters, events and a curated resource index maintained by practitioners.

    Why it made the list: The Slack behind this is where design system leads actually answer questions.

    DS process & docsfreeDesign Systems Communitydesign.systems

    design.systems preview
  21. 21

    DesignSystems.com

    Figma's design systems publication with long-form guides on tokens, iconography, spacing, content strategy and design operations.

    Why it made the list: Deep, non-promotional guides on foundations that Figma's product docs never cover.

    DS process & docsfreeFigmadesignsystems.com

    DesignSystems.com preview
  22. 22

    Duet

    LocalTapiola's insurance design system with web components, WCAG 2.1 AA conformance evidence and Finnish-language content rules.

    Why it made the list: Publishes actual accessibility test evidence rather than an accessibility claim.

    Public design systemsMITLocalTapioladuetds.com

    Duet preview
  23. 23

    Fluid Design System

    ENGIE's design system with web components, an energy-sector brand layer and documented eco-design and sustainability guidance.

    Why it made the list: Contains a real eco-design chapter — carbon-aware UI guidance, almost unique.

    Public design systemsMITENGIEengie.design

    Fluid Design System preview
  24. 24

    Geist

    Vercel's design system: colour and typography foundations, Geist Sans and Mono typefaces, icon set and React components.

    Why it made the list: The reference for restrained developer-product aesthetics, with the typefaces included free.

    Public design systemsfreeVercelvercel.com

    Geist preview

Questions

Should a small team build a design system?
Build tokens and a handful of primitives. Adopt an existing system for the rest until component churn justifies owning more.
Which public system is best for accessibility?
Government systems generally set the bar, because they are legally obliged to meet it and publish their testing.
All round-upsSearch all gemsNewest additions