---
name: fractal-foundations
description: "Apply, review, or extend Fractal color, typography, spacing, and responsive layout. Select the relevant foundation; full product pages use fractal-product-ui."
---

# Apply or extend foundations

Read [core](../../../../core.md). Load only the foundation governing the requested work:

| Work | Required reference | Bundle |
| --- | --- | --- |
| UI color, theme, semantic emphasis, or chemical element palettes | [Color](../../references/color.md) | `color-system` |
| Type hierarchy, font coverage, or typography tokens | [Typography](../../references/typography.md) | `typography` |
| Spacing, shared edges, responsiveness, or page geometry | [Layout](../../references/layout.md) | `layout` |

For a complete interface, use [product UI](../fractal-product-ui/SKILL.md) so all essential foundations are loaded together. For chart data marks, use [visualization](../../../data-visualization/skills/fractal-data-visualization/SKILL.md); UI accent choices do not select a chart palette.

## Decision sequence

1. Identify the artifact and scope. Product UI defaults do not become slide geometry.
2. Inspect the existing tokens, target theme, and actual rendered context. Use an existing semantic role before extending the system.
3. Select values through the reference's decision rules. Use the approved type tiers, named spacing tokens, and background-relative color treatments. Preserve scientific glyph coverage.
4. If a role is missing, explain the distinct need. Add a semantic alias to an existing primitive when possible. A primitive-scale change additionally requires [scale generation](../../references/color/scale-generation.md).
5. Update the owning source and affected implementations together after the ownership decision is established. Never document an alias that does not exist in implementation. Canonical tokens live in resources/tokens/; synchronize affected package tokens in the same session.

## Verify by domain

- Color: exact intended foreground/background pairs, final opacity, supported themes, status meaning, and non-color cues. For new scales, verify every stop and perceptual spacing, and deliver the requested swatches/contrast evidence.
- Typography: primary face and scientific fallback, allowed sizes and weights, role pairing, wrapping, and enlarged text. Package component APIs remain authoritative.
- Layout: common content edges, peer padding, divider conditions, visible clipping boundaries, control sizing, and actual touch targets. Off-grid spacing requires an explicit user request and the documented repair note.

Do not silently resolve contradictory source values. Ask for the missing decision and continue only independent work.
