Next phone
A playful industrial-design sandbox: each control changes a documented mesh, and a fixture design renders to a golden and a shareable state.
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/next-phone- Version
- 0.2.1
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/next-phone/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.Next phone
What this builds
A small studio where a person kits a handset: size, corner radius, camera bump, material. Each control changes a documented mesh parameter. A design can be serialised to a state string and a URL under
share_prefix. The object is a fictional device, not a branded flagship. A fixture design must render to a golden image and round-trip through the state string.Read
spekkr.inputs.jsonfirst.titlelabels the stage.bodyis the starting family.camera_lightandannotationschange the render.share_prefixis used when minting a URL.Out of scope
- A real manufacturer's name, logo, or CAD in the files.
- A production cost model or a factory export in this version.
- Network, accounts, or a public gallery in the checks.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Controls and mesh
- Parameters are listed in
design.md: width, height, thickness, radius, bump count, bump size, material. - Each control, moved to a stated value, changes only the documented mesh measure, within 0.05 mm.
- An illegal combination (radius more than half the smaller side, bump count 3 on
fold) is refused with a message.
Accept when: the parameter fixtures in
design.mdmatch the mesh measures, and the two illegal cases are refused.R2. Fixture design and share
fixtures/phone-alpha.jsonis a complete state. It renders to a golden (fixture-design) within the tolerance.- The state string is a compact query, documented in
design.md. Loading the string restores every parameter. - The share URL is
share_prefixplus the state string, and must be parsed back to the same state.
Accept when: the fixture renders to the golden, and a round-trip of its URL restores the same JSON (key order excepted).
R3. Files
- One command runs the mesh, refuse, render, and URL tests, and writes the four screenshots. No network.
Accept when: the command passes for both body families.
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
Each control changes a documented mesh measure, checked in millimetres. Illegal combinations are refused. A fixture design renders to a golden image and round-trips through a shareable state URL. No brand assets and 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 kit a device, how to share a state, and how to run the checks.
# Next phone ## What this builds A small studio where a person kits a handset: size, corner radius, camera bump, material. Each control changes a documented mesh parameter. A design can be serialised to a state string and a URL under `share_prefix`. The object is a fictional device, not a branded flagship. A fixture design must render to a golden image and round-trip through the state string. Read `spekkr.inputs.json` first. `title` labels the stage. `body` is the starting family. `camera_light` and `annotations` change the render. `share_prefix` is used when minting a URL. ## Out of scope - A real manufacturer's name, logo, or CAD in the files. - A production cost model or a factory export in this version. - Network, accounts, or a public gallery in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Controls and mesh - Parameters are listed in `design.md`: width, height, thickness, radius, bump count, bump size, material. - Each control, moved to a stated value, changes only the documented mesh measure, within 0.05 mm. - An illegal combination (radius more than half the smaller side, bump count 3 on `fold`) is refused with a message. Accept when: the parameter fixtures in `design.md` match the mesh measures, and the two illegal cases are refused. ### R2. Fixture design and share - `fixtures/phone-alpha.json` is a complete state. It renders to a golden (`fixture-design`) within the tolerance. - The state string is a compact query, documented in `design.md`. Loading the string restores every parameter. - The share URL is `share_prefix` plus the state string, and must be parsed back to the same state. Accept when: the fixture renders to the golden, and a round-trip of its URL restores the same JSON (key order excepted). ### R3. Files - One command runs the mesh, refuse, render, and URL tests, and writes the four screenshots. No network. Accept when: the command passes for both body families. ### 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 Each control changes a documented mesh measure, checked in millimetres. Illegal combinations are refused. A fixture design renders to a golden image and round-trips through a shareable state URL. No brand assets and 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 kit a device, how to share a state, and how to run the checks.
-
design.mdMesh parameters, illegal combinations, and the shareable state string.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.
Parameters (bar, millimetres)
Key Default Range width 71 60–80 height 147 120–170 thickness 8.2 6–12 radius 12 0–20, and at most half of min(width, height) bump_count 2 1, 2 or 3 (3 refused on fold) bump_size 10 8–16 material stonestone,glass,matteThe mesh measures (bounding box, bump centre positions) for the default and for the fixture are
fixtures/phone-measures.json.State string
A query such as
b=bar&w=71&h=147&t=8.2&r=12&c=2&s=10&m=stone. Unknown keys are refused. The fixture file is the authority for its own string.Screenshot tolerance
8 levels, 98% of pixels, 1600 by 1000, same camera for a given body family.
Inputs
Key Label Default Notes titleTitle Kit a handset Shown above the stage. share_prefixShare URL prefix https://example.invalid/p/ The prefix of a shareable URL. Tests use this exact host. camera_lightA second light on A rim light on the opposite side of the key light. annotationsShow size annotations off Dimension arrows on the render. bodyBody family bar A slab, or a two-leaf fold with a documented hinge gap. 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.mdA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/phone-alpha.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/phone-measures.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/handset.pngThe default midnight handset and the four mesh controls. 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.
- Each control changes a documented mesh measure, checked in millimetres. Illegal combinations are refused. A fixture design renders to a golden image and round-trips through a shareable state URL. No brand assets and 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. ## Parameters (bar, millimetres) | Key | Default | Range | | --- | --- | --- | | width | 71 | 60–80 | | height | 147 | 120–170 | | thickness | 8.2 | 6–12 | | radius | 12 | 0–20, and at most half of min(width, height) | | bump_count | 2 | 1, 2 or 3 (3 refused on fold) | | bump_size | 10 | 8–16 | | material | `stone` | `stone`, `glass`, `matte` | The mesh measures (bounding box, bump centre positions) for the default and for the fixture are `fixtures/phone-measures.json`. ## State string A query such as `b=bar&w=71&h=147&t=8.2&r=12&c=2&s=10&m=stone`. Unknown keys are refused. The fixture file is the authority for its own string. ## Screenshot tolerance 8 levels, 98% of pixels, 1600 by 1000, same camera for a given body family. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Kit a handset | Shown above the stage. | | `share_prefix` | Share URL prefix | https://example.invalid/p/ | The prefix of a shareable URL. Tests use this exact host. | | `camera_light` | A second light | on | A rim light on the opposite side of the key light. | | `annotations` | Show size annotations | off | Dimension arrows on the render. | | `body` | Body family | bar | A slab, or a two-leaf fold with a documented hinge gap. | ## 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. | | `fixtures/phone-alpha.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/phone-measures.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/handset.png` | The default midnight handset and the four mesh controls. | ## 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. Each control changes a documented mesh measure, checked in millimetres. Illegal combinations are refused. A fixture design renders to a golden image and round-trips through a shareable state URL. No brand assets and 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. - Controls and mesh (R1). Build what
R1. Controls and meshasks for, to the numbers indesign.md. In particular: Parameters are listed indesign.md: width, height, thickness, radius, bump count, bump size, material. Check: theR1. Controls and meshacceptance checks pass. - Fixture design and share (R2). Build what
R2. Fixture design and shareasks for, to the numbers indesign.md. In particular:fixtures/phone-alpha.jsonis a complete state. It renders to a golden (fixture-design) within the tolerance. Check: theR2. Fixture design and shareacceptance checks pass. - Files (R3). Build what
R3. Filesasks for, to the numbers indesign.md. In particular: One command runs the mesh, refuse, render, and URL tests, and writes the four screenshots. No network. Check: theR3. 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. **Controls and mesh (R1).** Build what `R1. Controls and mesh` asks for, to the numbers in `design.md`. In particular: Parameters are listed in `design.md`: width, height, thickness, radius, bump count, bump size, material. Check: the `R1. Controls and mesh` acceptance checks pass. 3. **Fixture design and share (R2).** Build what `R2. Fixture design and share` asks for, to the numbers in `design.md`. In particular: `fixtures/phone-alpha.json` is a complete state. It renders to a golden (`fixture-design`) within the tolerance. Check: the `R2. Fixture design and share` acceptance checks pass. 4. **Files (R3).** Build what `R3. Files` asks for, to the numbers in `design.md`. In particular: One command runs the mesh, refuse, render, and URL tests, and writes the four screenshots. No network. 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.
- 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.115 Nov 2026Names what it builds.
- 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.