auriFoundations
Every rule the components live by, written down. Nothing is hidden: if a value ships, it is documented here, and the swatches and demos on these pages render from the live tokens — they cannot drift from what you install.
Atoms and catalogs Why agent-facing components ship as evaluated vocabularies — and how catalogs mix on one surface.Colors The neutral ground, the green accent, five intents — and the budget that keeps color meaningful.Typography Three type roles, tabular numerals, why components inherit your font, and Geist on this site.Spacing The leaf-margin strategy: compact components, generous pages, streams that compose.Radii Four steps — 6, 10, 14, pill — and exactly which components use which.Motion The entrance, the stagger, interruptibility, and what reduced-motion users get instead.In-between states Skeleton, empty, error — components arrive before their data, so the gap is designed.Accessibility Enforced by the contract: pages that don’t exist until runtime can’t be audited, so the schema does it.Using auri with shadcn Two lanes, one system: the token bridge that makes agent surfaces inherit your shadcn theme.