# Build Neon HUD You were asked to build the spec `lume/neon-hud`, version 0.2.2, from Spekkr. A kit of clip-path panels and chrome for a film-like interface, checked by visual regression on a fixture page. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/lume/neon-hud/start.md`, before you go on. Published by lume, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `neon-hud`, inside the project you are working in. ```sh mkdir -p neon-hud && curl -fsSL https://spekkr.com/lume/neon-hud/bundle.tar.gz | tar -xz -C neon-hud ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/lume/neon-hud/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `lume/neon-hud` and the person's choices. ## 2. Record the person's choices Write `neon-hud/spekkr.inputs.json`. With every default it is: ```json { "spec": "lume/neon-hud", "version": "0.2.2", "inputs": { "accent": "#3ee0c4", "corners": true, "density": "film", "scanlines": true, "title": "Night circuit" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `title`, Title on the fixture page: any text. - `accent`, Accent colour: any text. - `scanlines`, Scanlines: `on` or `off`, written `true` or `false`. - `corners`, Cut corners: `on` or `off`, written `true` or `false`. - `density`, Density: one of `film`, `dense`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `neon-hud`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements and acceptance checks. - `design.md`: The fixture page, clip-path tokens, and visual-regression frames. - `tasks.md`: Build tasks in order, each with a check. - `reference/preview.html`: A working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file. - `reference/fonts/fonts.css`: Webfont faces for the reference preview. - `reference/fonts/Geist.ttf`: Geist variable typeface for the reference preview. - `reference/fonts/GeistMono.ttf`: Geist Mono variable typeface for the reference preview. - `reference/fonts/InstrumentSans.ttf`: Instrument Sans variable typeface for the reference preview.