An audit without a checklist is a conversation. An audit with a checklist is a methodology. The following structure is based on the five dimensions of a design system audit and makes results reproducible, comparable, and prioritizable.

Dimension 1: Token Architecture (10 Points)

Tokens exist in a structured format (JSON, DTCG). Clear separation into Primitive, Semantic, and Component Tokens. Aliasing is consistently used. Color palettes are complete and systematic. Typography tokens cover all levels. Spacing tokens follow a documented system. Token naming follows a documented convention. Dark mode is solvable via token modes. Orphaned tokens are identified. A build pipeline transforms tokens automatically.

Dimension 2: Component Library (12 Points)

All common UI patterns exist as components. Component APIs are consistent. All interactive components have correct ARIA attributes. Keyboard navigation works. Focus management is correctly implemented. Color contrasts meet WCAG 2.1 AA. Components use only design tokens – no hardcoded values. No duplicated components with different implementations. Responsive behavior is built into components. Bundle size is optimized. Components have defined states. Component stories exist for all variants.

Dimension 3: Documentation (10 Points)

A central documentation site exists. Each component has documentation with description, props table, and examples. Usage guidelines describe when to use which component. Do/Don’t examples illustrate correct usage. Code snippets are copyable and functional. Token documentation shows all available tokens. Documentation is current. A changelog documents breaking changes. Onboarding guide exists. Documentation is searchable.

Dimension 4: Processes (8 Points)

A defined process for component requests exists. Design and engineering work synchronously. A versioning schema is defined (SemVer). Breaking changes are communicated before release. A contribution model exists. Regular reviews assess system state. A defined owner/core team exists. Feedback channels are actively used.

Dimension 5: Tooling and Dependencies (10 Points)

All npm dependencies are inventoried and checked for vulnerabilities. No external CDN requests on page load. Analytics runs on EU-hosted infrastructure. Design tool dependency is documented with an exit strategy. The build pipeline runs on own infrastructure or EU SaaS. Licenses of all dependencies are verified. No single point of failure exists. Dependency updates are performed regularly. CI/CD pipeline is automated. Jurisdiction of critical dependencies is documented.

Scoring

Rating
Score
Meaning
Met
2
Fully implemented and documented
Partial
1
Present but incomplete or outdated
Not met
0
Missing or gravely deficient

Maximum score: 100. Below 40: fundamentals missing. 40–60: solid base with significant gaps. 60–80: good state, targeted optimization needed. Above 80: mature system, focus on continuous improvement.

Key Takeaways

  • 50 checkpoints across five dimensions make audits reproducible and comparable.
  • Token architecture and tooling/dependencies are the most frequently neglected dimensions.
  • The scoring approach (0/1/2 per point, max 100) enables comparison over time and between systems.
  • Dimension 5 (tooling and dependencies) is the sovereignty-specific differentiator.
  • Regular audits (biannually) prevent gradual system decay.