Design system audit

Foundations

Visual and experience rules that should become stable before the component catalog grows.

1stable
2partial
0missing

This documentation is also an audit.

It describes what exists today, flags inconsistencies, and proposes an order for turning them into shared rules.

FoundationStable

Colors

Expressive color with semantic roles and verifiable contrast.

5current decisions
0identified gaps
FoundationUsable

Typography

Space Grotesk for the interface, IBM Plex Mono for code and DM Sans 900 for game moments, with semantic roles.

3current decisions
1identified gaps
FoundationPartial

Spacing

A 4px base for controls and page composition.

1current decisions
1identified gaps
FoundationUsable

Radius & borders

One clean outline defines each piece.

3current decisions
0identified gaps
FoundationUsable

Shadows

Solid elevation without blur.

2current decisions
0identified gaps
FoundationUsable

States & motion

Appearance and behavior are documented together.

5current decisions
0identified gaps
FoundationUsable

Icons

Phosphor, with a consistent weight for each use.

3current decisions
0identified gaps
FoundationPartial

Accessibility

Keyboard, reading, contrast and motion are part of the design.

3current decisions
1identified gaps

How we will work

01

Document

Record what the product uses today without inventing an ideal version.

02

Compare

Find duplicated, arbitrary, or registry-missing values.

03

Decide

Turn findings into tokens, rules, and verifiable tests.