Technical explainer
How Loam keeps generated pages consistent.
Agents choose a document layout, compose with Loam classes, and preserve source for diagrams and code instead of inventing local design decisions.
Reusable source of truth
The repo owns the visual decisions: palette, typography, spacing, component states, and layout rhythm. Generated pages only assemble those primitives.
Agent contract
If a page needs a new visual pattern, add it to Loam intentionally instead of writing one-off CSS in the generated page.
Generation flow
The final page can link the public asset bundle or inline the CSS for a single-file handoff. Diagrams should be rendered before delivery.
Artifacts
| Artifact | Owned by | Purpose |
|---|---|---|
| CSS modules | Loam repo | Maintainable design system source. |
| Distribution CSS | Loam release | Static pages link or inline this file. |
| Agent guide | Loam docs | Rules for choosing layouts and components. |