/foundations

AI tools generate the same baseline for every product — Inter on white, blue accents, 8px radii, Tailwind’s default scale. /foundations replaces the inheritance with a starter system calibrated to your project’s character: color tokens, type scale, spacing, radius, motion, plus the primitive components everything else composes from.

/foundations is the commit-to-specifics step. It reads `.spruce.md` for context and `.sketch.md` for visual direction, then picks the specific values that express the character /sketch established — which typeface from the candidates, what specific OKLCH values for the color families /sketch named, what scale, what spacing rhythm, what specific durations within /sketch’s motion bands, what primitive components anchor the system. The creative work at this stage is selection and codification, not character discovery — that already happened in /sketch.

The output is end-to-end: design tokens across all domains, three to five primitive components implementing the system, plus a brief system guide. Significant decisions inside the codification step (accent strategy, type pairing, spacing base) are surfaced for your approval before commitment. When `.sketch.md` doesn’t exist, /foundations can still run — it makes the character calls inside itself but flags them clearly so they’re easy to redirect.

By default /foundations runs the full pass — color tokens, type scale, spacing, radius, motion, plus a small set of primitive components (button, card, link, heading). Pass a scope to focus on one layer, or describe what you need. Significant character shifts within each layer are surfaced for your approval rather than applied silently.