Neon HUD

A kit of clip-path panels and chrome for a film-like interface, checked by visual regression on a fixture page.

This is a creative tool spec on Spekkr, published by lume. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.

Spec
lume/neon-hud
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/lume/neon-hud/start.md.

Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.

Published by lume.

What does the result look like?

Neon HUD: heroNeon HUD: lockNeon HUD: loop

What can I customize?

Density How much chrome surrounds the content.

Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.

What do I get?

  • spec.md Requirements and acceptance checks.

    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.
    # 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.
    

    Open spec.md as plain text

  • design.md The fixture page, clip-path tokens, and visual-regression frames.

    Design

    This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold.

    Panels

    frame, readout, tick-list, hex-button, status-pip. Clip-path polygons are fixtures/hud-clips.json.

    Screenshot tolerance

    8 levels, 98% of pixels, 1600 by 1000, frozen.

    Inputs

    KeyLabelDefaultNotes
    titleTitle on the fixture pageNight circuitShown in the main panel.
    accentAccent colour#3ee0c4A #rrggbb used for edges and a scanline wash.
    scanlinesScanlinesonA faint horizontal wash.
    cornersCut cornersonClip-path notches on the panels.
    densityDensityfilmHow much chrome surrounds the content.

    Acceptance at the defaults

    The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins.

    FixtureRole
    fixtures/hud-clips.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/hud-page.htmlA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.md must name the new path.

    Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy.

    Screenshots

    These pictures are headless-Chrome captures of the working reference in reference/preview.html, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel.

    FileWhat it shows
    shots/circuit.pngNight circuit, accent #3ee0c4, clip-path panels and a lock reticle.

    How to verify

    1. Run the checks at the default inputs, without a network.
    2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
    3. Repeat once at the person's inputs when they differ from the defaults.
    4. 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.
    # Design
    
    This file fixes the parts that are easy to get wrong. The language and
    tools are up to you, as long as the numbers here hold.
    
    ## Panels
    
    `frame`, `readout`, `tick-list`, `hex-button`, `status-pip`. Clip-path
    polygons are `fixtures/hud-clips.json`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels, 1600 by 1000, frozen.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title on the fixture page | Night circuit | Shown in the main panel. |
    | `accent` | Accent colour | #3ee0c4 | A #rrggbb used for edges and a scanline wash. |
    | `scanlines` | Scanlines | on | A faint horizontal wash. |
    | `corners` | Cut corners | on | Clip-path notches on the panels. |
    | `density` | Density | film | How much chrome surrounds the content. |
    
    ## Acceptance at the defaults
    
    The numbers, names and fixture paths already in this file are the
    authority. Where a later table or a shipped fixture file disagrees with
    prose, the table or the fixture wins.
    
    | Fixture | Role |
    | --- | --- |
    | `fixtures/hud-clips.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/hud-page.html` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    
    Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement
    names another size. Tolerance, unless a tighter figure is given above: 8
    levels, 98% of pixels, with motion, cursors and clocks frozen as this file
    says. A build's goldens are of that build; they do not have to match a
    shipped reference preview pixel-for-pixel if the tool or the type is
    different, but they do have to match this file's layout, counts and copy.
    
    ## Screenshots
    
    These pictures are headless-Chrome captures of the working reference in
    `reference/preview.html`, at the default inputs. They are not drawings of a
    product that has not been built. The first picture is the one Spekkr shows on
    the spec's card. A build may ship its own goldens; those goldens are of that
    build and do not have to match these frames pixel-for-pixel.
    
    | File | What it shows |
    | --- | --- |
    | `shots/circuit.png` | Night circuit, accent #3ee0c4, clip-path panels and a lock reticle. |
    
    
    ## How to verify
    
    1. Run the checks at the default inputs, without a network.
    
    2. Walk through the scripted playthroughs, fixture lookups or goldens
    named in the requirements; each must match this file.
    
    3. Repeat once at the person's inputs when they differ from the defaults.
    
    4. 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.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    Tasks

    Work in order. Finish a task's check before starting the next.

    1. Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read spekkr.inputs.json first. Check: a blank or heading page loads, and an empty test run passes.
    2. The kit on a page (R1). Build what R1. The kit on a page asks for, to the numbers in design.md. In particular: The fixture page fixtures/hud-page.html (plus the kit) at default inputs matches the fixture-page golden. Check: the R1. The kit on a page acceptance checks pass.
    3. Tokens and files (R2). Build what R2. Tokens and files asks for, to the numbers in design.md. In particular: Accent colour of the edges is accent, checked as a computed style on .hud-edge. Check: the R2. Tokens and files acceptance checks pass.
    4. Inputs (R3). Build what R3. Inputs asks for, to the numbers in design.md. In particular: 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. Check: the R3. Inputs acceptance checks pass.
    5. Checks and report (R4). Build what R4. Checks and report asks for, to the numbers in design.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the R4. Checks and report acceptance checks pass.
    6. Goldens. Capture the frames named in design.md at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose.
    7. Finish. Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in spec.md is true.
    # Tasks
    
    Work in order. Finish a task's check before starting the next.
    
    1. **Set up.** Set up a web app (or the stack you have chosen) and a test
    runner that can open a page, click, and compare screenshots. Read
    `spekkr.inputs.json` first.
       Check: a blank or heading page loads, and an empty test run passes.
    
    2. **The kit on a page (R1).** Build what `R1. The kit on a page` asks
    for, to the numbers in `design.md`. In particular: The fixture page
    `fixtures/hud-page.html` (plus the kit) at default inputs matches the
    `fixture-page` golden.
       Check: the `R1. The kit on a page` acceptance checks pass.
    
    3. **Tokens and files (R2).** Build what `R2. Tokens and files` asks for,
    to the numbers in `design.md`. In particular: Accent colour of the edges
    is `accent`, checked as a computed style on `.hud-edge`.
       Check: the `R2. Tokens and files` acceptance checks pass.
    
    4. **Inputs (R3).** Build what `R3. Inputs` asks for, to the numbers in
    `design.md`. In particular: 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.
       Check: the `R3. Inputs` acceptance checks pass.
    
    5. **Checks and report (R4).** Build what `R4. Checks and report` asks
    for, to the numbers in `design.md`. In particular: One command runs every
    acceptance check at the defaults and at the person's inputs, including
    golden frames where a requirement asks for them.
       Check: the `R4. Checks and report` acceptance checks pass.
    
    6. **Goldens.** Capture the frames named in `design.md` at the defaults,
    with motion frozen where the file says so. Compare them within the stated
    tolerance.
       Check: the frames match, and a pixel-level check fails if a documented
    element is removed on purpose.
    
    7. **Finish.** Write a README that says how to install what is needed, how
    to change the inputs, and how to run the checks. Run the one command from
    a clean folder.
       Check: every item under Definition of done in `spec.md` is true.
    

    Open tasks.md as plain text

  • 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.

Is it for me?

Platforms
web
Tools
TypeScript, CSS

What does it need?

Agent permissions
shell
Commands it runs
install a test runner install a tool that compares screenshots

What changed?

  • 0.2.215 Nov 2026Names what it builds.
  • 0.2.114 Nov 2026Add animated loop to the listing shots.
  • 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
  • 0.1.014 Nov 2026First version.

For agents: start.md says how to build this spec, spec.json holds everything on this page, and bundle.tar.gz holds its files.