Atomic layers field guide

Explains the actual seven Loom Site layers with concrete examples and links into their contracts. Distinguishes atomic composition from organisational inheritance.

Organism · draft · v1.0.0 · owner: Site system lead · contract 19 of 20 points (open: figma)

Do and don't

Do: Actual hierarchy

Rendered by atomic-guide.ts

Open example: Atomic layers field guide · Do: Actual hierarchy Use the full-page example to follow page links.

Seven levels matching LAYERS.

Do: Japanese hierarchy

Rendered by atomic-guide.ts

Open example: Atomic layers field guide · Do: Japanese hierarchy Use the full-page example to follow page links.

Translated explanations with the same examples.

Don't: Not an organisation tree

Rendered by atomic-guide.ts

Open example: Atomic layers field guide · Don't: Not an organisation tree Use the full-page example to follow page links.

Brand and region are a different model.

Don't: Not a mandatory dependency chain

Rendered by atomic-guide.ts

Open example: Atomic layers field guide · Don't: Not a mandatory dependency chain Use the full-page example to follow page links.

A template can use an atom directly; levels describe composition roles.

Rules

RuleWhyCheck
Positive specimens declare their rendered initial state and document language; each registered visual variant has a positive example.Machine and Library consumers need the same examples without turning declarations into execution evidence.Automated: tests/unit/v4-example-coverage.test.ts
Every row must match a real layer and its example must have that layer in the registry.The field guide must teach the actual system, not an attractive invented hierarchy.Automated: tests/unit/site-identity.test.ts

API

PropTypeRequiredDefaultWhat it does
instanceKeystringNo"atomic-guide"Stable specimen ID scope. Use distinct keys for multiple guides in one document; up to 64 letters, digits, hyphens or underscores, beginning with a letter.
langen | jaNo"en"Guide language.

Contract details

The full contract: identity, anatomy, variants, states, tokens, layout, motion, accessibility, content, tests

Identity

AspectValue
Idatomic-guide
LayerOrganisms
Categorydiagram
OwnerSite system lead
Statusdraft
Version1.0.0
Sourceapps/showcase/site/system/organisms/atomic-guide.ts (private repository; the contract and the render function are this one module)
VersionDateChange
1.0.02026-10-27Created from the owner-selected V4 direction (D-SITE-019).

Use when

  • Explaining how the website is built from its own system. Why: Every abstract layer has a real, inspectable example.

Do not use when

  • Explaining global, regional or product governance layers. Why: Those are organisational scopes, not atomic composition levels.

Anatomy

PartWhat it is
rootOrdered list of seven levels
levelLayer name, visual composition and actual example link
noteComposition does not require every dependency to visit every level
dependenciesActual madeOf edges from the representative elements
operatingSequenceSource Signal/Pattern/Decision/Rule/Action model, labelled separately

Made of: heading, text-link, tokens-component, button, cta-pair, header, hero.

Used in: pages directly.

Variants

VariantWhenWhy
defaultWherever the page declaration places it.One shape per job keeps pages predictable.

States

StateRendered or not applicable
defaultdefault
hoverInteractive links retain their text and visible affordance on hover.
focus-visibleContract links, actual Button/CtaPair specimens, disclosure summaries and scrollable specimen regions take focus in reading order; the outer guide does not take focus.
activeEnter activates the focused link; native buttons also accept Space. Parent content does not move.
disabledNot applicable: Atomic guide has nothing to disable.
loadingNot applicable: Atomic guide is rendered at build time and is complete when the page loads.
emptyNot applicable: Content is generated from registered system definitions and has no empty-list variant.
errorNot applicable: Atomic guide shows no data that can fail.
currentNot applicable: Atomic guide has no current item.
visitedNot applicable: These navigational links keep their semantic colour; browser history does not imply task completion.
expandedNot applicable: Atomic guide does not open or close.

Tokens

PartToken
--atomic-guide-preview-min-widthvar(--w-text)
--atomic-guide-cottonvar(--cotton)
--atomic-guide-surfacevar(--surface)
--atomic-guide-inkvar(--ink)
--atomic-guide-ink-mutedvar(--ink-2)
--atomic-guide-linevar(--line)
--atomic-guide-line-strongvar(--line-strong)
--atomic-guide-rulevar(--rule-hair)
--atomic-guide-gapvar(--space-6)
--atomic-guide-gap-smallvar(--space-3)
--atomic-guide-gap-mediumvar(--space-4)
--atomic-guide-marginvar(--space-9)
--atomic-guide-titlevar(--type-h3)
--atomic-guide-captionvar(--type-small)
--atomic-guide-linkvar(--link)
--atomic-guide-targetvar(--space-11)
--atomic-guide-indigovar(--indigo)
--atomic-guide-tealvar(--teal)
--atomic-guide-saffronvar(--saffron)
--atomic-guide-maddervar(--madder)
--atomic-guide-focusvar(--focus)
--atomic-guide-focus-widthvar(--rule)
--atomic-guide-focus-offsetvar(--space-2)

Layout

AspectValue
breakpointsThe example spans the guide width up to 600 px. At viewport widths of 700 px and above, the native Hero specimen retains at least --atomic-guide-preview-min-width (720 px through --w-text) inside its own scroll region, matching the tile two-column breakpoint.
wrappingGuide copy wraps. Native Header/Hero specimens may scroll inside their labelled, keyboard-focusable regions; the surrounding page must not overflow horizontally.
textExpansionJapanese and expanded text grow within the guide. Native specimen geometry is preserved with local scrolling rather than smaller type or clipped words.

Spacing and rhythm

AspectValue
internal--space-6 per layer
external--space-9
rhythmSeven connected levels in reading order.

Motion

AspectValue
NoneNo intrinsic element animation. The optional claude-entrance consumer profile may translate below-fold structure once (20px, --dur-weave, --ease-enter, --stagger); reduced motion disables it. This preserved baseline entrance is separate from element playback.

Runtime and reuse

  1. Render-only element; mount any registered child enhancements separately. Preserve required Site CSS, fonts, responsive and locale rules from nativeElement.

Accessibility passport

AspectValue
roleOrdered list of seven composition layers with links and actual component specimens
nameVisible layer names and contract-link text
keyboardTab follows document order; Enter follows links or toggles specimen disclosures. Focus a specimen region to scroll it with arrow/Page keys; its embedded Header/Hero controls remain inert.
focusLinks, disclosure summaries and scrollable specimen regions have a visible ring; the outer guide is not a focus stop
screenReaderThe composition and operating sequence are separately labelled; dependencies are real links, not an inferred compulsory chain
contrastCopy uses system ink/link roles on cloth and surface
targetLinks use the component target token; embedded controls own their targets

Content

SlotLengthVoice
exampleOne actual elementUse the registry's real name and link.

Good: “Atoms · Button”

Bad: “Signal is an atomic component layer”

Japanese: All layer explanations and examples have Japanese text; contract links open the English library.

Icons and illustrations

None: this element uses no icon or illustration of its own.

Decisions and exceptions

Usage

220 uses across the built pages (measured by npm run site:system).

Tests

AspectValue
unittests/unit/site-system.test.ts: renders every do and don't example through the registry and checks the classes it owns
visualNot yet: there are no screenshot baselines; the Library page is checked for sideways scroll at 1440 px by tests/site/system.spec.ts
a11ytests/site/system.spec.ts: axe (0 serious or critical) on the element's Library page in light and dark
parityscripts/site/system/check.ts: Library examples are rendered by the same render function the site imports

Figma

not-yet: The Loom Site Figma library is the last stage of the plan; this element is not mapped yet.

Open in Storybook

Start with a conversation about your system.

We read your system, show you what we found, and agree with your team what to fix first.