Hand whiteboard

An infinite, slightly imperfect hand-drawn canvas: create, move, arrow and export are tested, and a fixture scene round-trips.

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

Build this spec

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

Hand whiteboard: heroHand whiteboard: loop

What can I customize?

Export format How a board is saved. Tests always write json, and svg when both or svg is chosen.

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.

    Hand whiteboard

    What this builds

    An infinite canvas for boxes, rough lines, arrows, and text, in the spirit of a hand-drawn whiteboard. The lines are imperfect, but a seed makes the roughness repeatable. A fixture scene must round-trip through the file format. Create, move, arrow, and export are tested. This is an original tool, not a copy of someone else's board, and it does not use their file format as a required input.

    Read spekkr.inputs.json first. title is on an empty board. roughness and a seed (fixed in tests) shape the lines. export chooses the file format. grid and arrows change the chrome and whether arrow heads exist.

    Out of scope

    • A live multiplayer room in the checks (a later hook may add it).
    • Someone else's file format as a required import.
    • Network or a cloud document in the checks.

    Requirements

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

    R1. Create, move, arrow
    • A box, a line, a text, and (if arrows is on) an arrow can be created with documented default sizes.
    • A move of a box by (dx, dy) moves it, and any arrow attached to it keeps its attachment.
    • The fixture script fixtures/board-ops.json ends in the scene in fixtures/board-scene.json.

    Accept when: the scripted operations produce the scene file, including the attached arrow.

    R2. Round-trip and export
    • The json file of the fixture scene, loaded into a fresh board, produces the same scene (ids may be stable as in the file).
    • An svg export, when that format is on, contains a path or a line for every stroke, and a text for every text, and is well-formed XML.
    • A golden canvas shot of the loaded fixture, seed 4, roughness 0.8, matches fixture-scene.

    Accept when: the json round-trips, the svg parses and lists the stated elements, and the golden matches.

    R3. Files
    • One command runs the operations, the round-trip, the svg parse, and writes the four screenshots. No network. Roughness uses seed 4.

    Accept when: the command passes for every export format.

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

    Verification

    Create, move, arrow, and export are tested with a script that reaches a documented scene. That scene round-trips through the json format, and an svg export parses. A golden canvas shot is taken with a pinned roughness seed. No network and no third-party file format requirement.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to draw, how to export, and how to run the checks.
    # Hand whiteboard
    
    ## What this builds
    
    An infinite canvas for boxes, rough lines, arrows, and text, in the spirit
    of a hand-drawn whiteboard. The lines are imperfect, but a seed makes the
    roughness repeatable. A fixture scene must round-trip through the file
    format. Create, move, arrow, and export are tested. This is an original
    tool, not a copy of someone else's board, and it does not use their file
    format as a required input.
    
    Read `spekkr.inputs.json` first. `title` is on an empty board. `roughness`
    and a seed (fixed in tests) shape the lines. `export` chooses the file
    format. `grid` and `arrows` change the chrome and whether arrow heads
    exist.
    
    ## Out of scope
    
    - A live multiplayer room in the checks (a later hook may add it).
    - Someone else's file format as a required import.
    - Network or a cloud document in the checks.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Create, move, arrow
    
    - A box, a line, a text, and (if `arrows` is on) an arrow can be created
      with documented default sizes.
    - A move of a box by (dx, dy) moves it, and any arrow attached to it keeps
      its attachment.
    - The fixture script `fixtures/board-ops.json` ends in the scene in
      `fixtures/board-scene.json`.
    
    Accept when: the scripted operations produce the scene file, including the
    attached arrow.
    
    ### R2. Round-trip and export
    
    - The json file of the fixture scene, loaded into a fresh board, produces
      the same scene (ids may be stable as in the file).
    - An svg export, when that format is on, contains a path or a line for
      every stroke, and a text for every text, and is well-formed XML.
    - A golden canvas shot of the loaded fixture, seed 4, roughness 0.8,
      matches `fixture-scene`.
    
    Accept when: the json round-trips, the svg parses and lists the stated
    elements, and the golden matches.
    
    ### R3. Files
    
    - One command runs the operations, the round-trip, the svg parse, and
      writes the four screenshots. No network. Roughness uses seed 4.
    
    Accept when: the command passes for every export format.
    
    ### R4. 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.
    
    ## Verification
    
    Create, move, arrow, and export are tested with a script that reaches a
    documented scene. That scene round-trips through the json format, and an
    svg export parses. A golden canvas shot is taken with a pinned roughness
    seed. No network and no third-party file format requirement.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to draw, how to export, and how to run the checks.
    

    Open spec.md as plain text

  • design.md The scene format, scripted operations, and the export round-trip.

    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.

    Scene format

    A json document with objects: each has id, type (box, line, arrow, text), geometry, and text. The fixture file is the authority. Attachments are { "from": id, "to": id, "end": "arrow" }.

    Screenshot tolerance

    8 levels, 98% of pixels, camera at the fixture's view box, seed 4.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA messy boardShown in a corner of an empty board.
    roughnessLine roughness0.8From 0 (straight) to 1.5. Tests pin the seed so roughness is deterministic.
    gridDot gridonA faint background grid.
    arrowsArrow headsonLines can end in an arrow.
    exportExport formatbothHow a board is saved. Tests always write json, and svg when both or svg is chosen.

    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/board-ops.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/board-scene.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/board.pngA messy board at roughness 0.8, two cards arrowed, export still to do.

    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. Create, move, arrow, and export are tested with a script that reaches a documented scene. That scene round-trips through the json format, and an svg export parses. A golden canvas shot is taken with a pinned roughness seed. No network and no third-party file format requirement.
    # 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.
    
    ## Scene format
    
    A json document with `objects`: each has `id`, `type` (`box`, `line`,
    `arrow`, `text`), geometry, and text. The fixture file is the authority.
    Attachments are `{ "from": id, "to": id, "end": "arrow" }`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels, camera at the fixture's view box, seed 4.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A messy board | Shown in a corner of an empty board. |
    | `roughness` | Line roughness | 0.8 | From 0 (straight) to 1.5. Tests pin the seed so roughness is deterministic. |
    | `grid` | Dot grid | on | A faint background grid. |
    | `arrows` | Arrow heads | on | Lines can end in an arrow. |
    | `export` | Export format | both | How a board is saved. Tests always write json, and svg when both or svg is chosen. |
    
    ## 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/board-ops.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/board-scene.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/board.png` | A messy board at roughness 0.8, two cards arrowed, export still to do. |
    
    
    ## 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. Create, move, arrow, and export are tested with a script that reaches a
    documented scene. That scene round-trips through the json format, and an
    svg export parses. A golden canvas shot is taken with a pinned roughness
    seed. No network and no third-party file format requirement.
    

    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. Create, move, arrow (R1). Build what R1. Create, move, arrow asks for, to the numbers in design.md. In particular: A box, a line, a text, and (if arrows is on) an arrow can be created with documented default sizes. Check: the R1. Create, move, arrow acceptance checks pass.
    3. Round-trip and export (R2). Build what R2. Round-trip and export asks for, to the numbers in design.md. In particular: The json file of the fixture scene, loaded into a fresh board, produces the same scene (ids may be stable as in the file). Check: the R2. Round-trip and export acceptance checks pass.
    4. Files (R3). Build what R3. Files asks for, to the numbers in design.md. In particular: One command runs the operations, the round-trip, the svg parse, and writes the four screenshots. No network. Roughness uses seed 4. Check: the R3. Files acceptance checks pass.
    5. Inputs (R4). Build what R4. 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 R4. Inputs 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. **Create, move, arrow (R1).** Build what `R1. Create, move, arrow` asks
    for, to the numbers in `design.md`. In particular: A box, a line, a text,
    and (if `arrows` is on) an arrow can be created with documented default
    sizes.
       Check: the `R1. Create, move, arrow` acceptance checks pass.
    
    3. **Round-trip and export (R2).** Build what `R2. Round-trip and export`
    asks for, to the numbers in `design.md`. In particular: The json file of
    the fixture scene, loaded into a fresh board, produces the same scene (ids
    may be stable as in the file).
       Check: the `R2. Round-trip and export` acceptance checks pass.
    
    4. **Files (R3).** Build what `R3. Files` asks for, to the numbers in
    `design.md`. In particular: One command runs the operations, the
    round-trip, the svg parse, and writes the four screenshots. No network.
    Roughness uses seed 4.
       Check: the `R3. Files` acceptance checks pass.
    
    5. **Inputs (R4).** Build what `R4. 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 `R4. Inputs` 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/Newsreader.ttf Newsreader variable typeface for the reference preview.
  • reference/fonts/Newsreader-Italic.ttf Newsreader italic 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.