Fluid paint
A viscous, smudgeable paint, slower and oilier than an ink demo, with a scripted stroke, colour mixing tests, and a golden frame.
This is an interactive visual spec on Spekkr, published by nova. 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
nova/fluid-paint- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/fluid-paint/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 nova.
What does the result look like?
What can I customize?
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.mdRequirements and acceptance checks.Fluid paint
What this builds
A painting canvas where paint is viscous. A stroke sits, then smudges when you drag it, more like oil than like a thin ink fluid. Colour mixing is tested: two fixture colours, smudged, produce a documented third. A scripted stroke yields a golden frame. This is a different toy from a full-screen ink sandbox, and the two should not share a name or a look.
Read
spekkr.inputs.jsonfirst.titleis in the margin.thicknessis viscosity.paperis the ground.wetandmixingchange drying and mixing.Out of scope
- A print-ready colour-managed art tool.
- Network or a community canvas in the checks.
- A real-world pigment model beyond the mix table in design.md.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. A stroke and a smudge
fixtures/paint-stroke.jsonis a list of pointer samples. At thickness 0.7, wet on, the canvas at tick 40 and at tick 160 (after a smudge listed in the file) matches dye checksums in the sibling file.- If
wetis off, a stroke older than 2 seconds does not move under a later smudge; the dry fixture checks this.
Accept when: the wet checksums match, and the dry fixture's second checksum equals its first (no smudge).
R2. Mixing
- When
mixingis on, a dab of colour A and a dab of colour B, smudged as infixtures/paint-mix.json, produce at a listed pixel a colour within 8 levels of the documented mix. - When
mixingis off, that pixel stays within 8 levels of A or of B, not the mix. - A and B and the mix are listed as
#rrggbbin the file.
Accept when: the mix pixel matches in both option states.
R3. Frames and files
- Goldens: the first stroke, a smudge, a mixed dab, and a dried stroke that refused to smudge.
- One command runs the checksum, dry, and mix tests, and writes the frames. No network. A CPU reference is preferred in CI.
Accept when: the command passes at thickness 0.3 and 0.7, and the frames match the goldens.
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
A scripted stroke yields checksums and a golden frame. A wet smudge moves paint; a dried stroke does not. Colour mixing is tested at a documented pixel against a mix table, and is skipped when the option is off. A CPU reference is preferred in CI. No network.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to paint, how to run the checks, and how this differs from a thin-ink fluid demo.
# Fluid paint ## What this builds A painting canvas where paint is viscous. A stroke sits, then smudges when you drag it, more like oil than like a thin ink fluid. Colour mixing is tested: two fixture colours, smudged, produce a documented third. A scripted stroke yields a golden frame. This is a different toy from a full-screen ink sandbox, and the two should not share a name or a look. Read `spekkr.inputs.json` first. `title` is in the margin. `thickness` is viscosity. `paper` is the ground. `wet` and `mixing` change drying and mixing. ## Out of scope - A print-ready colour-managed art tool. - Network or a community canvas in the checks. - A real-world pigment model beyond the mix table in design.md. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. A stroke and a smudge - `fixtures/paint-stroke.json` is a list of pointer samples. At thickness 0.7, wet on, the canvas at tick 40 and at tick 160 (after a smudge listed in the file) matches dye checksums in the sibling file. - If `wet` is off, a stroke older than 2 seconds does not move under a later smudge; the dry fixture checks this. Accept when: the wet checksums match, and the dry fixture's second checksum equals its first (no smudge). ### R2. Mixing - When `mixing` is on, a dab of colour A and a dab of colour B, smudged as in `fixtures/paint-mix.json`, produce at a listed pixel a colour within 8 levels of the documented mix. - When `mixing` is off, that pixel stays within 8 levels of A or of B, not the mix. - A and B and the mix are listed as `#rrggbb` in the file. Accept when: the mix pixel matches in both option states. ### R3. Frames and files - Goldens: the first stroke, a smudge, a mixed dab, and a dried stroke that refused to smudge. - One command runs the checksum, dry, and mix tests, and writes the frames. No network. A CPU reference is preferred in CI. Accept when: the command passes at thickness 0.3 and 0.7, and the frames match the goldens. ### 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 A scripted stroke yields checksums and a golden frame. A wet smudge moves paint; a dried stroke does not. Colour mixing is tested at a documented pixel against a mix table, and is skipped when the option is off. A CPU reference is preferred in CI. No network. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to paint, how to run the checks, and how this differs from a thin-ink fluid demo.
-
design.mdScripted strokes, drying, and the colour-mix table.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.
Mix table
The documented mix of A
#c43c2cand B#e4d39a, at equal wetness, is#d48b5c(a simple subtractive-ish blend defined exactly infixtures/paint-mix.json). Tests use the file.Screenshot tolerance
12 levels, 96% of pixels for wet paint; 8 levels, 98% for the dried frame. Checksums on a CPU reference are exact.
Inputs
Key Label Default Notes titleTitle A slow, oily stroke Shown in a margin. thicknessThickness 0.7 From 0.2 to 1, how viscous the paint is. wetKeep the paint wet on If off, a stroke dries after 2 seconds and no longer smudges. mixingMix on the canvas on A second colour smudged into the first produces a documented mix. paperPaper cream The ground colour. 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/paint-mix.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/paint-stroke.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.mdmust 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/stroke.pngA slow, oily scripted stroke at thickness 0.7. How to verify
- Run the checks at the default inputs, without a network.
- Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
- Repeat once at the person's inputs when they differ from the defaults.
- A scripted stroke yields checksums and a golden frame. A wet smudge moves paint; a dried stroke does not. Colour mixing is tested at a documented pixel against a mix table, and is skipped when the option is off. A CPU reference is preferred in CI. No network.
# 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. ## Mix table The documented mix of A `#c43c2c` and B `#e4d39a`, at equal wetness, is `#d48b5c` (a simple subtractive-ish blend defined exactly in `fixtures/paint-mix.json`). Tests use the file. ## Screenshot tolerance 12 levels, 96% of pixels for wet paint; 8 levels, 98% for the dried frame. Checksums on a CPU reference are exact. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A slow, oily stroke | Shown in a margin. | | `thickness` | Thickness | 0.7 | From 0.2 to 1, how viscous the paint is. | | `wet` | Keep the paint wet | on | If off, a stroke dries after 2 seconds and no longer smudges. | | `mixing` | Mix on the canvas | on | A second colour smudged into the first produces a documented mix. | | `paper` | Paper | cream | The ground colour. | ## 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/paint-mix.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/paint-stroke.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/stroke.png` | A slow, oily scripted stroke at thickness 0.7. | ## 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. A scripted stroke yields checksums and a golden frame. A wet smudge moves paint; a dried stroke does not. Colour mixing is tested at a documented pixel against a mix table, and is skipped when the option is off. A CPU reference is preferred in CI. No network.
-
tasks.mdBuild tasks in order, each with a check.Tasks
Work in order. Finish a task's check before starting the next.
- 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.jsonfirst. Check: a blank or heading page loads, and an empty test run passes. - A stroke and a smudge (R1). Build what
R1. A stroke and a smudgeasks for, to the numbers indesign.md. In particular:fixtures/paint-stroke.jsonis a list of pointer samples. At thickness 0.7, wet on, the canvas at tick 40 and at tick 160 (after a smudge listed in the file) matches dye checksums in the sibling file. Check: theR1. A stroke and a smudgeacceptance checks pass. - Mixing (R2). Build what
R2. Mixingasks for, to the numbers indesign.md. In particular: Whenmixingis on, a dab of colour A and a dab of colour B, smudged as infixtures/paint-mix.json, produce at a listed pixel a colour within 8 levels of the documented mix. Check: theR2. Mixingacceptance checks pass. - Frames and files (R3). Build what
R3. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the first stroke, a smudge, a mixed dab, and a dried stroke that refused to smudge. Check: theR3. Frames and filesacceptance checks pass. - Inputs (R4). Build what
R4. Inputsasks for, to the numbers indesign.md. In particular: The build readsspekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: theR4. Inputsacceptance checks pass. - Goldens. Capture the frames named in
design.mdat 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. - 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.mdis 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. **A stroke and a smudge (R1).** Build what `R1. A stroke and a smudge` asks for, to the numbers in `design.md`. In particular: `fixtures/paint-stroke.json` is a list of pointer samples. At thickness 0.7, wet on, the canvas at tick 40 and at tick 160 (after a smudge listed in the file) matches dye checksums in the sibling file. Check: the `R1. A stroke and a smudge` acceptance checks pass. 3. **Mixing (R2).** Build what `R2. Mixing` asks for, to the numbers in `design.md`. In particular: When `mixing` is on, a dab of colour A and a dab of colour B, smudged as in `fixtures/paint-mix.json`, produce at a listed pixel a colour within 8 levels of the documented mix. Check: the `R2. Mixing` acceptance checks pass. 4. **Frames and files (R3).** Build what `R3. Frames and files` asks for, to the numbers in `design.md`. In particular: Goldens: the first stroke, a smudge, a mixed dab, and a dried stroke that refused to smudge. Check: the `R3. Frames and 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.
- 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
-
reference/preview.htmlA 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.cssWebfont faces for the reference preview. -
reference/fonts/Geist.ttfGeist variable typeface for the reference preview. -
reference/fonts/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces italic 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 runnerinstall 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.