# Prototype Instructions

Run the local server yourself and open the preview in the browser available to this environment. Do not give the user server-start instructions when you can run it.

Before making substantial visual changes, use the Product Design plugin's `get-context` skill when the visual source is unclear or no longer matches the current goal. When the user gives durable prototype-specific design feedback, preferences, or decisions, record them in `AGENTS.md`.

When implementing from a selected generated mock, treat that image as the source of truth for layout, component anatomy, density, spacing, color, typography, visible content, and hierarchy.

Build app UI in `src/`. Keep `.openai/hosting.json`, `worker/index.js`, `scripts/prepare-sites-build.mjs`, and `tests/sites-worker.test.mjs` intact so the same local prototype can be handed to Sites. Before a Sites handoff, run `npm run build` and `npm run test:sites`; the build must leave `dist/client/index.html`, `dist/server/index.js`, and `dist/.openai/hosting.json`.

## Selected Nexus direction

- Source visual: `reference/selected-option-2.png`, the second displayed
  Run-Control concept selected on 2026-07-27.
- This is a desktop-only controlled prototype. Do not create a mobile view,
  phone shell, mobile breakpoint, or standalone Mobile Chat destination.
- Preserve the selected spatial-orchestration composition and the existing
  Nexus Galaxy/Glass design contract.
- Agent nodes, approval steps, event rows, and provider/session metadata must
  open useful detail views.
- Keep all behavior authored and local. Do not call Nexus, OpenClaw, OpenAI, or
  another backend, and label the surface as mock data.