Foundations
The token layer every component is built on. Restyle the system by remapping these — components consume tokens, never raw values.
Tokens
Styling flows through semantic roles (bg-brand-solid, border-input, …) — a token audit fails the build on any raw hex or hand-set length, so “100% tokenized” is enforced, not aspirational.
ColorSemantic surfaces and status colors, light and dark.TypographyThe type scale and text styles.SpacingThe spacing ramp and density-scaled control sizes.Radius & shadowCorner radii and elevation tokens.MotionDurations and easing curves — the Glide vibe.Axestone · appearance · variant — what each styling axis means, and why the names are enforced.
Accessibility contracts
garn ships 104 machine-checkable accessibility contracts across 46 components — accessible names, labelled controls, dialog titles, keyboard models. Each is data, not prose: it names its severity and the condition it applies under, so the garn_audit MCP tool (and CI) can lint a composition against them. Every component page lists its own contracts under Accessibility.