# Neon HUD ## What this builds A design kit of panels, clip-path corners, typography, and edges that make a page feel like a film interface. It is a look, not a surveillance product. A fixture page uses the kit, and visual regression checks the page and the parts. The shapes and the type are original. No trademarked film title is used. Read `spekkr.inputs.json` first. `title` and `accent` are on the fixture page. `density` changes how much chrome is drawn. `scanlines` and `corners` turn those effects on. ## Out of scope - A real vehicle or weapon interface. - Network or a theme marketplace. - A 3D cockpit in this version. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. The kit on a page - The fixture page `fixtures/hud-page.html` (plus the kit) at default inputs matches the `fixture-page` golden. - A panel catalogue (each panel type at rest) matches `panel-set`. - A form using the kit's inputs and a primary action matches `form-chrome`. Accept when: the three frames match the goldens, and a fourth `dense` frame matches when density is dense. ### R2. Tokens and files - Accent colour of the edges is `accent`, checked as a computed style on `.hud-edge`. - One command builds the fixture page, reads the token, and writes the four screenshots. No network. Accept when: the accent matches the input, and the command passes with scanlines and corners on and off (siblings or a documented skip of frames that only change a wash). ### R3. Inputs - The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification Visual regression covers the kit on a fixture page, a panel catalogue, a form, and a dense variant. The accent token is read back from computed style. No network and no trademarked film branding. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to use a panel, how to change the accent, and how to run the checks.