design-system

Topics in the source

• Design System — Token Core
• Color strategy
• Typography scale
• Spacing
• Touch targets
• The design-system.md output — canonical format
• Reference index (data lives here, read from source, never restated above)
• Next

The token-strategy core: OKLCH-only color rules for new tokens, neutral tinting (chroma 0.005-0.015, never pure gray), the accent-commitment levels (restrained/committed/full palette/drenched), the typography scale (ratio, line-height, measure), the 8pt spacing grid, and platform touch-target minimums. Also defines the canonical output format of design-system.md — the file the harness gates on — including its 4 hard requirements (the ## Design Reference heading, a real inspiration URL, at least one chroma-positive OKLCH token, and the hard-forbidden font exclusions). This is routing step 1 of design-method/SKILL.md: read it before design-web, design-webapp, design-ios, or design-android, and before picking or auditing a single color/type/spacing value. Single source for token strategy — not values, values live in references/.md and are read from there, never re-derived here. design-method/SKILL.md reads this file unconditionally as routing step 1, once per task, before dispatching to any move or target skill — that read is also what advances the harness past phase 0. If a design question is purely about a token (a color, a type pair, a spacing value) this file plus its reference in

This is an excerpt. Refer to the complete source and its current requirements.