temps-design-system

# Temps design system The design system is a sandbox app plus a component package. Everything a UI task needs is in the repo; do not invent tokens, colours or page shapes. | What | Where | |---|---| | Rules digest for agents (read first, imperative, short) | `design-system/docs/RULES.md` | | Brand guidelines (why the rules exist) | `design-system/docs/brand-guidelines.md` | | Handoff: tokens, primitive catalogue, page templates, responsive, keyboard | `design-system/docs/design-system-handoff.md` | | Component package consumed by screens | `web/packages/ds` (`@temps-sdk/ds`) | | Consumer setup (a plugin, an outside app): install, `op.css`, `@source`, the skin class, fonts | `web/packages/ds/README.md` | | Reference implementation of every screen | `design-system/src/sections/ConsoleV1*.tsx` | | Browsable guide, component gallery, console mockups | `cd design-system && bun install && bun run dev` → `/guide`, `/op-components`, `/v1` | ## Scope boundary What exists today, stated plainly so nobody assumes more: **the production console (`web/src`, rsbuild) does not import `@temps-sdk/ds` yet.** What is built is the system (the docs), the package, and the sandbox that renders every primitive and every screen shape against it. Console migration happens screen by screen, on a schedule, not as a side effect of another task. - **Redesign work** (new screens on `@temps-sdk/ds`, the sandbox, the landing and status page mockups): this skill applies in full. - **Legacy console** (`...