Design Tokens
The Mzizi design system uses 8 categories of semantic tokens that flow from L1 through all layers. These replace raw color values with meaningful, theme-adaptive tokens.
Token Categories
Section titled “Token Categories”| Category | CSS Prefix | Values |
|---|---|---|
| Status | –status-* | success, warning, error, info, neutral |
| Severity | –severity-* | low, moderate, high, severe, extreme, cold |
| Notification | –notification-* | success, warning, error, info |
| Connection | –connection-* | online, syncing, cached, offline |
| Verification | –tier-* | unverified, community, otp, government, licensed |
| Crypto | –crypto-* | quantumSafe, classical, weak, none |
| Moderation | –moderation-* | approved, pending, flagged, rejected |
| Service Health | –health-* | operational, degraded, outage, maintenance |
Usage Pattern
Section titled “Usage Pattern”/* In L1 tokens */--status-success: var(--color-malachite, #64FFDA);--status-error: var(--destructive, #FF5252);
/* In L2-L7 components */background-color: var(--status-success, var(--color-malachite, #64FFDA));The fallback chain ensures: semantic token → mineral token → hex fallback.
Wiring Through Layers
Section titled “Wiring Through Layers”- L1 defines the tokens
- L2 status-bearing primitives (status-dot, kpi-card, service-health-card) use them
- L3 brand components with status indicators use them
- L4 safety gates use them for gate state visualization
- L5 resilience components use connection/health tokens
- L6 pages use only semantic CSS vars (bg-primary, text-foreground)
- L7 shell uses connection tokens for connectivity-bar
- L8 assurance uses health tokens for platform-health