Build UI Toolkit for Meta Ray-Ban Display interfaces

Build with the toolkit components as behavioral primitives, not as visual inspiration for custom HTML. Let the library own material, shape, clipping, typography, interaction state, focus motion, and popup placement.

Start every task

1. Read ../uit-screen-architecture-web/SKILL.md, choose one legal route skeleton, and record the single vertical owner for every route/pager page.
2. Read only the relevant references below, plus references/quality-checklist.md before completion.
3. Implement from this skill library's public API guidance. Inspect one exact exported prop type only when a selected API remains ambiguous or typecheck reports a mismatch. Do not systematically browse implementation, tests, gallery pages, package directories, or icon directories before coding.
4. Use a gallery page only as a concrete API example after the skills and public documentation leave a specific composition unresolved. Gallery code is not production architecture and never overrides the skill contract.

Never infer an API from another platform or invent an unsupported prop, slot, variant, or behavior.