Color — Foundations

Verdict. Author in OKLCH (perceptually uniform L/C/H). Ship sRGB-safe values by default, upgrade to display-p3 under @supports for vibrancy. Theme through semantic tokens only — components never touch a raw --brand-500

Core Design Literacy

Copyright-safe synthesis of durable visual fundamentals (contrast, repetition, alignment, proximity, hierarchy, gestalt). Operational checks - One dominant focal point per view - Alignment to an intentional grid - Hier

International Typography

Japanese - Pair Latin + JP intentionally; avoid default system-only stacks for brand work. - Line length and leading differ from Latin; test 日本語 body copy. - Respect 禁則 and palt judiciously. RTL - Mirror layout, not me

Platform Literacy

Before inventing custom UI, understand the platform's grammar (Apple HIG, Android/Material, Web). Rules 1. Prefer native navigation patterns on iOS/Android unless brand requires divergence and you redesign the full st

Spacing & Layout — Canonical Foundation

The skeleton everything else hangs on. Get the rhythm right and a UI feels engineered; get it wrong and no color or type can save it. This module defines the 8pt spacing scale, the radius scale, breakpoints, fluid contai

Design Tokens — The Canonical Token Contract

This is the file every other module references. Buttons, cards, dialogs, type ramps — all of them consume the names defined here, never raw values. Theming (light → dark → high-contrast) is a values swap on stable name

Typography

The verdict. Canonical typography foundation for the design system. Copy-paste-ready, framework-agnostic CSS first, then a React 19 + Tailwind v4 + Motion reference. Every value maps to the canonical token contract (--te