Data shader

A shader scene driven by fixture time series, with documented uniforms and goldens for calm and chaotic inputs, no live feed.

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/data-shader
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/lume/data-shader/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?

Data shader: heroData shader: loop

What can I customize?

Look Two original scenes, same uniforms.

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.

    Data shader

    What this builds

    A scene whose look is a shader, driven by a small set of uniforms from a time series: wind, brightness, a pulse. The series is a fixture file, not a live market or weather feed. Tests map fixture values to documented uniforms and take golden frames for a calm series and a chaotic one. A hook fails if a live feed host is contacted.

    Read spekkr.inputs.json first. title is in a corner. series chooses a fixture. look is the scene. labels and play change the chrome. Tests pin an instant in the series.

    Out of scope

    • A live market, weather, or sensor feed in the checks.
    • A paid data API in the checks.
    • A trading claim.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. Uniforms
    • Each instant in fixtures/series-calm.json and fixtures/series-chaotic.json maps to uniforms listed in fixtures/shader-uniforms.json, within 1e-4.
    • A pinned instant (calm at t = 12 s, chaotic at t = 12 s) is used for the goldens.
    • A fetch hook fails if a known market or weather host is contacted.

    Accept when: every listed instant's uniforms match, and the hook stays quiet.

    R2. Frames and files
    • Goldens: calm, chaotic, a readout of the calm instant, and a frozen (play off) calm view, which should match calm.
    • One command maps the series, hooks, and writes the frames. No network.

    Accept when: the command passes for both looks (sibling goldens), and the frames match.

    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

    Fixture time-series values map to documented shader uniforms, within 1e-4. Golden frames cover calm and chaotic inputs. A fetch hook fails if a live market or weather feed is contacted. No paid API and no network are required.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to add a series, how uniforms are named, and how to run the checks.
    # Data shader
    
    ## What this builds
    
    A scene whose look is a shader, driven by a small set of uniforms from a
    time series: wind, brightness, a pulse. The series is a fixture file, not
    a live market or weather feed. Tests map fixture values to documented
    uniforms and take golden frames for a calm series and a chaotic one. A
    hook fails if a live feed host is contacted.
    
    Read `spekkr.inputs.json` first. `title` is in a corner. `series` chooses
    a fixture. `look` is the scene. `labels` and `play` change the chrome.
    Tests pin an instant in the series.
    
    ## Out of scope
    
    - A live market, weather, or sensor feed in the checks.
    - A paid data API in the checks.
    - A trading claim.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Uniforms
    
    - Each instant in `fixtures/series-calm.json` and
      `fixtures/series-chaotic.json` maps to uniforms listed in
      `fixtures/shader-uniforms.json`, within 1e-4.
    - A pinned instant (calm at t = 12 s, chaotic at t = 12 s) is used for the
      goldens.
    - A fetch hook fails if a known market or weather host is contacted.
    
    Accept when: every listed instant's uniforms match, and the hook stays
    quiet.
    
    ### R2. Frames and files
    
    - Goldens: calm, chaotic, a readout of the calm instant, and a frozen
      (play off) calm view, which should match calm.
    - One command maps the series, hooks, and writes the frames. No network.
    
    Accept when: the command passes for both looks (sibling goldens), and the
    frames match.
    
    ### 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
    
    Fixture time-series values map to documented shader uniforms, within 1e-4.
    Golden frames cover calm and chaotic inputs. A fetch hook fails if a live
    market or weather feed is contacted. No paid API and no network are
    required.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to add a series, how uniforms are named, and how to
      run the checks.
    

    Open spec.md as plain text

  • design.md Fixture series, uniform mapping, and calm versus chaotic goldens.

    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.

    Mapping

    A documented linear map from series columns to uniform names, in the uniforms file. The shader must read those names. Calm and chaotic are original, invented series, not real market data.

    Screenshot tolerance

    8 levels, 98% of pixels (12 if a GPU run is allowed; CI should prefer a CPU or a software renderer if goldens drift).

    Inputs

    KeyLabelDefaultNotes
    titleTitleA day as weatherShown in a corner.
    seriesDefault seriescalmA fixture id: calm or chaotic, or another shipped series.
    labelsShow a readoutonThe current fixture values as numbers.
    playPlay the seriesonIf off, a single frozen instant is shown. Tests pin the instant anyway.
    lookLookfieldTwo original scenes, same uniforms.

    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/series-calm.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/series-chaotic.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/shader-uniforms.jsonA 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/evening.pngThe calm series as an evening frame, uniforms driven by fixture time series.

    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. Fixture time-series values map to documented shader uniforms, within 1e-4. Golden frames cover calm and chaotic inputs. A fetch hook fails if a live market or weather feed is contacted. No paid API and no network are required.
    # 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.
    
    ## Mapping
    
    A documented linear map from series columns to uniform names, in the
    uniforms file. The shader must read those names. Calm and chaotic are
    original, invented series, not real market data.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels (12 if a GPU run is allowed; CI should prefer a
    CPU or a software renderer if goldens drift).
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A day as weather | Shown in a corner. |
    | `series` | Default series | calm | A fixture id: calm or chaotic, or another shipped series. |
    | `labels` | Show a readout | on | The current fixture values as numbers. |
    | `play` | Play the series | on | If off, a single frozen instant is shown. Tests pin the instant anyway. |
    | `look` | Look | field | Two original scenes, same uniforms. |
    
    ## 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/series-calm.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/series-chaotic.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/shader-uniforms.json` | 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/evening.png` | The calm series as an evening frame, uniforms driven by fixture time series. |
    
    
    ## 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. Fixture time-series values map to documented shader uniforms, within
    1e-4. Golden frames cover calm and chaotic inputs. A fetch hook fails if a
    live market or weather feed is contacted. No paid API and no network are
    required.
    

    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. Uniforms (R1). Build what R1. Uniforms asks for, to the numbers in design.md. In particular: Each instant in fixtures/series-calm.json and fixtures/series-chaotic.json maps to uniforms listed in fixtures/shader-uniforms.json, within 1e-4. Check: the R1. Uniforms acceptance checks pass.
    3. Frames and files (R2). Build what R2. Frames and files asks for, to the numbers in design.md. In particular: Goldens: calm, chaotic, a readout of the calm instant, and a frozen (play off) calm view, which should match calm. Check: the R2. Frames 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. **Uniforms (R1).** Build what `R1. Uniforms` asks for, to the numbers
    in `design.md`. In particular: Each instant in `fixtures/series-calm.json`
    and `fixtures/series-chaotic.json` maps to uniforms listed in
    `fixtures/shader-uniforms.json`, within 1e-4.
       Check: the `R1. Uniforms` acceptance checks pass.
    
    3. **Frames and files (R2).** Build what `R2. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: calm, chaotic, a
    readout of the calm instant, and a frozen (play off) calm view, which
    should match calm.
       Check: the `R2. Frames 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/Unbounded.ttf Unbounded variable typeface for the reference preview.

Is it for me?

Platforms
web
Tools
TypeScript, WebGL

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.