Lisp sculpt
A live-coded 3D art studio: fixture programs produce a golden render, and an optional mesh is checked watertight.
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/lisp-sculpt- Version
- 0.2.2
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/lisp-sculpt/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?
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.Lisp sculpt
What this builds
A studio where a small language and a few sliders describe a 3D form, rendered live. The language is a tiny Lisp (or a prefix form of the same tree) with math and a handful of signed-distance primitives. Fixture programs produce a golden render. When the mesh option is on, the extracted isosurface is watertight. The language and the fixtures are original.
Read
spekkr.inputs.jsonfirst.titlelabels the editor.languageis the spelling.resolutionis the extract grid.meshandsliderschange what is written and shown.Out of scope
- A general programming environment or a package manager.
- Network or a public sketch gallery in the checks.
- A physically printed sculpture in the checks.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Fixture programs
fixtures/orb.lispandfixtures/twist.lisp(and prefix twins if that language is on) render at the default camera to the goldensorb-fixtureandtwisted-fixture.- A slider listed in a program, set to a documented value, changes a measure of the field or the mesh (for example the orb's bounding radius) to the value in
fixtures/sculpt-measures.json, within 0.02 units.
Accept when: both fixture renders match the goldens, and the listed slider measure matches.
R2. Mesh
- If
meshis on, the extract at resolution 128 of the orb fixture is a single closed solid: a mesh library reports it watertight, with no self-intersections above a tiny tolerance indesign.md. - The bounding box of that mesh matches the file within 0.05 units.
Accept when: the mesh is watertight and the box matches, when the option is on.
R3. Files
- One command runs both languages' fixtures, the slider measure, the mesh check, and writes the four screenshots (the fourth is the mesh or a second camera if mesh is off).
- No network.
Accept when: the command passes at resolution 64 and 128, for both languages.
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
Fixture programs produce golden renders in both spellings of the language. A slider changes a documented measure. When the mesh option is on, the extracted orb is watertight and its bounding box matches a file. No network and no physical print.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to write a form, how to export a mesh, and how to run the checks.
# Lisp sculpt ## What this builds A studio where a small language and a few sliders describe a 3D form, rendered live. The language is a tiny Lisp (or a prefix form of the same tree) with math and a handful of signed-distance primitives. Fixture programs produce a golden render. When the mesh option is on, the extracted isosurface is watertight. The language and the fixtures are original. Read `spekkr.inputs.json` first. `title` labels the editor. `language` is the spelling. `resolution` is the extract grid. `mesh` and `sliders` change what is written and shown. ## Out of scope - A general programming environment or a package manager. - Network or a public sketch gallery in the checks. - A physically printed sculpture in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Fixture programs - `fixtures/orb.lisp` and `fixtures/twist.lisp` (and prefix twins if that language is on) render at the default camera to the goldens `orb-fixture` and `twisted-fixture`. - A slider listed in a program, set to a documented value, changes a measure of the field or the mesh (for example the orb's bounding radius) to the value in `fixtures/sculpt-measures.json`, within 0.02 units. Accept when: both fixture renders match the goldens, and the listed slider measure matches. ### R2. Mesh - If `mesh` is on, the extract at resolution 128 of the orb fixture is a single closed solid: a mesh library reports it watertight, with no self-intersections above a tiny tolerance in `design.md`. - The bounding box of that mesh matches the file within 0.05 units. Accept when: the mesh is watertight and the box matches, when the option is on. ### R3. Files - One command runs both languages' fixtures, the slider measure, the mesh check, and writes the four screenshots (the fourth is the mesh or a second camera if mesh is off). - No network. Accept when: the command passes at resolution 64 and 128, for both languages. ### 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 Fixture programs produce golden renders in both spellings of the language. A slider changes a documented measure. When the mesh option is on, the extracted orb is watertight and its bounding box matches a file. No network and no physical print. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to write a form, how to export a mesh, and how to run the checks.
-
design.mdThe small language, fixture programs, slider measures, and watertight meshes.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.
Language
A minimal Lisp: numbers, symbols,
(op …), ops+ - * / min max sqrt sin, and SDF opssphere box union sub smooth, plus aparamform that exposes a slider. The prefix spelling is the same tree without parentheses, as in the twin files.Mesh
Watertight means every edge is shared by exactly two faces, and the solid volume is positive. Tolerance for a stray intersection is 1e-4.
Screenshot tolerance
8 levels, 98% of pixels, camera in
fixtures/sculpt-camera.json.Inputs
Key Label Default Notes titleTitle A form from a few lines Shown above the editor. resolutionMarch resolution 128 64, 128 or 256, the extract grid. meshAlso write a mesh on An STL or OBJ of the isosurface, checked watertight when on. slidersShow sliders on Each parameter in the program gets a slider. languageLanguage tiny-lisp Two spellings of the same small language. 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/sculpt-camera.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/sculpt-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/form.pngThe fixture program rendered at resolution 128: a smooth union of two spheres. 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.
- Fixture programs produce golden renders in both spellings of the language. A slider changes a documented measure. When the mesh option is on, the extracted orb is watertight and its bounding box matches a file. No network and no physical print.
# 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. ## Language A minimal Lisp: numbers, symbols, `(op …)`, ops `+ - * / min max sqrt sin`, and SDF ops `sphere box union sub smooth`, plus a `param` form that exposes a slider. The prefix spelling is the same tree without parentheses, as in the twin files. ## Mesh Watertight means every edge is shared by exactly two faces, and the solid volume is positive. Tolerance for a stray intersection is 1e-4. ## Screenshot tolerance 8 levels, 98% of pixels, camera in `fixtures/sculpt-camera.json`. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A form from a few lines | Shown above the editor. | | `resolution` | March resolution | 128 | 64, 128 or 256, the extract grid. | | `mesh` | Also write a mesh | on | An STL or OBJ of the isosurface, checked watertight when on. | | `sliders` | Show sliders | on | Each parameter in the program gets a slider. | | `language` | Language | tiny-lisp | Two spellings of the same small language. | ## 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/sculpt-camera.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/sculpt-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/form.png` | The fixture program rendered at resolution 128: a smooth union of two spheres. | ## 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 programs produce golden renders in both spellings of the language. A slider changes a documented measure. When the mesh option is on, the extracted orb is watertight and its bounding box matches a file. No network and no physical print.
-
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. - Fixture programs (R1). Build what
R1. Fixture programsasks for, to the numbers indesign.md. In particular:fixtures/orb.lispandfixtures/twist.lisp(and prefix twins if that language is on) render at the default camera to the goldensorb-fixtureandtwisted-fixture. Check: theR1. Fixture programsacceptance checks pass. - Mesh (R2). Build what
R2. Meshasks for, to the numbers indesign.md. In particular: Ifmeshis on, the extract at resolution 128 of the orb fixture is a single closed solid: a mesh library reports it watertight, with no self-intersections above a tiny tolerance indesign.md. Check: theR2. Meshacceptance checks pass. - Files (R3). Build what
R3. Filesasks for, to the numbers indesign.md. In particular: One command runs both languages' fixtures, the slider measure, the mesh check, and writes the four screenshots (the fourth is the mesh or a second camera if mesh is off). 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. **Fixture programs (R1).** Build what `R1. Fixture programs` asks for, to the numbers in `design.md`. In particular: `fixtures/orb.lisp` and `fixtures/twist.lisp` (and prefix twins if that language is on) render at the default camera to the goldens `orb-fixture` and `twisted-fixture`. Check: the `R1. Fixture programs` acceptance checks pass. 3. **Mesh (R2).** Build what `R2. Mesh` asks for, to the numbers in `design.md`. In particular: If `mesh` is on, the extract at resolution 128 of the orb fixture is a single closed solid: a mesh library reports it watertight, with no self-intersections above a tiny tolerance in `design.md`. Check: the `R2. Mesh` acceptance checks pass. 4. **Files (R3).** Build what `R3. Files` asks for, to the numbers in `design.md`. In particular: One command runs both languages' fixtures, the slider measure, the mesh check, and writes the four screenshots (the fourth is the mesh or a second camera if mesh is off). 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/GeistMono.ttfGeist Mono 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?
- Kind
- creative tool
- Platforms
- web
- Tools
- TypeScript, WebGL
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshotsinstall a mesh library, such as trimesh
What changed?
- 0.2.215 Nov 2026Names what it builds.
- 0.2.115 Nov 2026Render a clear 12-sphere bloom on a torus, and add an animated loop.
- 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.