Pixel canvas

A shared pixel canvas: multi-client paint, cooldown and conflict tests against a local server, with a golden board and a time-lapse frame.

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

Build this spec

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

Pixel canvas: heroPixel canvas: loop

What can I customize?

Palette A shipped 16-colour set.

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.

    Pixel canvas

    What this builds

    A shared pixel board. Several clients paint, one pixel at a time, with a cooldown. Conflicts (two paints on the same pixel) are resolved by a documented rule. Tests run a local in-process server and two or more clients, not a public host. A golden board and a time-lapse frame are taken. The palette is original.

    Read spekkr.inputs.json first. title labels the board. size and cooldown set the rules. palette is the colour set. timelapse and grid change what is recorded and drawn.

    Out of scope

    • A public internet board in the checks.
    • A live moderation team or accounts, in this version.
    • Network beyond the local server.

    Requirements

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

    R1. Paint, cooldown, conflict
    • A paint at (x, y) with a colour id is accepted if the client is off cooldown, and the pixel becomes that colour.
    • A second paint from the same client before cooldown ms (virtual clock) is refused.
    • Two clients painting the same pixel in the same tick: the lower client id wins, as in design.md. The losing paint is reported as a conflict.

    Accept when: the script in fixtures/pixel-ops.json ends in the board in fixtures/pixel-board.json, including a refused cooldown and a documented conflict.

    R2. Frames and files
    • Goldens: an empty board, two clients mid-script, the final board, and a time-lapse frame (the last snapshot, or a collage if the file says so).
    • One command starts the local server, runs the script on a virtual clock, and writes the frames. No public network.

    Accept when: the command passes at size 32 and 64, and the frames match the goldens.

    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

    Multi-client paint, cooldown, and conflict are tested against a local in-process server and a virtual clock. The final board matches a file. A golden board and a time-lapse frame are checked. No public host and no real 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 run a local room, how conflicts are decided, and how to run the checks.
    # Pixel canvas
    
    ## What this builds
    
    A shared pixel board. Several clients paint, one pixel at a time, with a
    cooldown. Conflicts (two paints on the same pixel) are resolved by a
    documented rule. Tests run a local in-process server and two or more
    clients, not a public host. A golden board and a time-lapse frame are
    taken. The palette is original.
    
    Read `spekkr.inputs.json` first. `title` labels the board. `size` and
    `cooldown` set the rules. `palette` is the colour set. `timelapse` and
    `grid` change what is recorded and drawn.
    
    ## Out of scope
    
    - A public internet board in the checks.
    - A live moderation team or accounts, in this version.
    - Network beyond the local server.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Paint, cooldown, conflict
    
    - A paint at (x, y) with a colour id is accepted if the client is off
      cooldown, and the pixel becomes that colour.
    - A second paint from the same client before `cooldown` ms (virtual clock)
      is refused.
    - Two clients painting the same pixel in the same tick: the lower client
      id wins, as in `design.md`. The losing paint is reported as a conflict.
    
    Accept when: the script in `fixtures/pixel-ops.json` ends in the board in
    `fixtures/pixel-board.json`, including a refused cooldown and a documented
    conflict.
    
    ### R2. Frames and files
    
    - Goldens: an empty board, two clients mid-script, the final board, and a
      time-lapse frame (the last snapshot, or a collage if the file says so).
    - One command starts the local server, runs the script on a virtual clock,
      and writes the frames. No public network.
    
    Accept when: the command passes at size 32 and 64, and the frames match
    the goldens.
    
    ### 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
    
    Multi-client paint, cooldown, and conflict are tested against a local
    in-process server and a virtual clock. The final board matches a file. A
    golden board and a time-lapse frame are checked. No public host and no
    real 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 run a local room, how conflicts are decided, and
      how to run the checks.
    

    Open spec.md as plain text

  • design.md Local multi-client paints, cooldown, conflict, and the golden board.

    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.

    Conflict

    The server applies paints in client-id then arrival-id order. The first applied paint in that order wins. The fixture script is the authority.

    Screenshot tolerance

    8 levels, 98% of pixels. The final board's pixels must also match the file exactly.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA shared gridShown above the board.
    sizeBoard size64Width and height, 32, 64 or 128.
    cooldownCooldown, ms200From 0 to 2000, the wait between paints for one client.
    timelapseRecord a time-lapseonA frame every N paints, written at the end.
    gridShow a faint gridoffAt large zooms.
    palettePaletteclassicA shipped 16-colour set.

    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
    design.mdA 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/grid.pngA 64×64 shared grid mid-paint, cooldown 200 ms.

    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. Multi-client paint, cooldown, and conflict are tested against a local in-process server and a virtual clock. The final board matches a file. A golden board and a time-lapse frame are checked. No public host and no real 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.
    
    ## Conflict
    
    The server applies paints in client-id then arrival-id order. The first
    applied paint in that order wins. The fixture script is the authority.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. The final board's pixels must also match the file
    exactly.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A shared grid | Shown above the board. |
    | `size` | Board size | 64 | Width and height, 32, 64 or 128. |
    | `cooldown` | Cooldown, ms | 200 | From 0 to 2000, the wait between paints for one client. |
    | `timelapse` | Record a time-lapse | on | A frame every N paints, written at the end. |
    | `grid` | Show a faint grid | off | At large zooms. |
    | `palette` | Palette | classic | A shipped 16-colour set. |
    
    ## 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 |
    | --- | --- |
    | `design.md` | 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/grid.png` | A 64×64 shared grid mid-paint, cooldown 200 ms. |
    
    
    ## 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. Multi-client paint, cooldown, and conflict are tested against a local
    in-process server and a virtual clock. The final board matches a file. A
    golden board and a time-lapse frame are checked. No public host and no
    real 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. Paint, cooldown, conflict (R1). Build what R1. Paint, cooldown, conflict asks for, to the numbers in design.md. In particular: A paint at (x, y) with a colour id is accepted if the client is off cooldown, and the pixel becomes that colour. Check: the R1. Paint, cooldown, conflict 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: an empty board, two clients mid-script, the final board, and a time-lapse frame (the last snapshot, or a collage if the file says so). 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. **Paint, cooldown, conflict (R1).** Build what `R1. Paint, cooldown,
    conflict` asks for, to the numbers in `design.md`. In particular: A paint
    at (x, y) with a colour id is accepted if the client is off cooldown, and
    the pixel becomes that colour.
       Check: the `R1. Paint, cooldown, conflict` 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: an empty board, two
    clients mid-script, the final board, and a time-lapse frame (the last
    snapshot, or a collage if the file says so).
       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/GeistMono.ttf Geist Mono 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

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.