Constant
Type, geometry, icon language, density and interaction.
A warm editorial layer meets a calm product interface. Each product remains recognisable by colour; everything else is a shared, precise, usable foundation.
01 / Family principles
Type, geometry, icon language, density and interaction.
Product colour, content, data and internal mark gesture.
Would this still feel related in grayscale? If yes, it belongs.
02 / Universal type & iconography
Newsreader
Display, insight statements and report titles.
Geist
Navigation, UI, forms, tables and body copy.
Geist Mono
Metrics, dates, metadata and technical detail.
03 / Product colour architecture
Each product owns one hue, expressed through a five-step tonal ramp. Components, typography, shape language and information hierarchy remain shared.
Growth intelligence
Product intelligence
People intelligence
Profit intelligence
| Semantic role | Shared token | Use |
|---|---|---|
| Primary | --product-primary | Key actions, selected state, emphasis |
| Hover | --product-primary-hover | Darker step in the product tonal ramp |
| Subtle | --product-primary-subtle | Lightest step in the product tonal ramp |
| Accent | --product-accent | Lighter step in the product tonal ramp |
| Ring | --product-ring | Central product primary |
Static button specimens use the accessible deep tone from each product ramp.
Static04 / Shared components
Static specimens| Signal | Owner | Status |
|---|---|---|
| Expansion account | AK | Review |
| Margin variance | LS | Resolved |
The same buttons, controls, card geometry, density, borders and focus states appear in every product. Product colour only enters where meaning benefits from it.
05 / System playground
Switch the product to inspect the exact tokens, controls and layouts that should change—while the underlying interface stays consistent.
Template gallery
A shared page architecture in product context.
Operating signal
48,204
Priority
Review expansion accounts
Open queue →06 / System registry
The design system is versioned source code, documented contracts and shared templates—not a collection of screenshots.
System changes require cross-product visual review, keyboard and contrast checks, reduced-motion verification, and a changelog entry.