Use Forma as a presentation boundary, not an application runtime.
Agents reuse canonical patterns, preserve native semantics, and leave behavioral and domain authority in the systems that own it.
Required sequence
- Identify the user task and domain state.
- Find the closest canonical pattern under
patterns/. - Use its public
<forma-…>authoring tag around the canonical pattern. - Preserve its semantic elements, class structure, labels, IDs, and ARIA relationships.
- Supply application content and rendered state.
- Put non-native behavior in the consuming application/Limen.
- Keep legal transitions, permissions, obligations, and scoring in Ordo/application state.
- Run repository and site verification before claiming completion.
Boundary ownership
| Concern | Owner |
|---|---|
| Typography, color, spacing, layout, responsive presentation | Forma |
| Checked/open/required/disabled and native state | Native HTML rendered by the application |
| Async search, ranking movement, rule editing | Application / Limen |
| Legal transitions, capabilities, obligations, permissions | Ordo/application domain state |
| Scores and assessment interpretation | Application domain logic |
Do not
- Register Forma's
<forma-…>authoring tags withcustomElements.define(); they are intentionally inert wrappers. - Add runtime JavaScript or WebAssembly to Forma.
- Replace native HTML only to obtain a custom appearance.
- Create duplicate components for presets an existing semantic pattern represents.
- Infer domain meaning from color, order, or CSS state.
- Make drag, hover, pointer input, or color the only usable path.
- Fork a pattern in an application merely to change visual styling.
Mobile is part of the component contract
Every Forma pattern must recompose at 320 CSS px without changing its semantic meaning or domain authority.
- No essential page-level horizontal scrolling.
- No hover-only, drag-only, pointer-only, or color-only interaction.
- Critical actions remain reachable when layouts collapse.
- Side-by-side comparisons stack with explicit labels.
- Tables provide a usable narrow projection when ordinary columns cannot fit.
- Target sizes should be approximately 44×44 CSS px where practical.
- Deep-link and URL-backed state keeps the same meaning when its visual control changes form.
- Reduced-motion and forced-colors behavior still applies on mobile.
Character grids
For terminal-style, keyboard-first screens use the CharacterGrid family (patterns/character-grid*.html). Declare cell coordinates, write runs in row-major order, keep fields native, and leave key mapping, Enter/Clear/Reset/PF processing, transitions, and reveal orchestration to Limen/application code. See docs/CHARACTER-GRID-AUTHORING.md.
Use the catalog
Every component page answers "what is the smallest correct HTML?" in its Basic example, then shows scenario and mobile examples, the native attributes, the CSS hooks derived from the shipped stylesheet, states, accessibility responsibilities, and related components. Pages share one structure: learn one, read all.
- All components A–Z and one overview page per family.
- site-manifest.json: every component's name, tag, family, summary, behavior owner, canonical pattern path, documented attributes, CSS hooks, keyboard behavior, related components and docs URL.
- To document a new component, follow
docs/CATALOG-AUTHORING.md;npm run catalog:checkfails until the entry is complete.
Build and verify
npm install
npm run build
npm run check
npm run catalog:check
npm run site:check
./ros registry check
./ros validate
The repository source of truth for this contract is docs/AGENT-USAGE.md.