Drum machine
A tight in-browser sequencer: a fixture pattern renders a buffer whose onsets and bar length match the grid, plus UI pattern tests.
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/drum-machine- Version
- 0.2.2
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/drum-machine/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.Drum machine
What this builds
A drum sequencer you can jam with at once: a grid of steps, a few voices, a tempo, and a play control. The samples are original or permissively licensed, not a ripped commercial machine, and the product does not use a trademarked model number in its id or its name. A fixture pattern is rendered offline to a buffer; onset times and the bar length must match the grid. UI tests cover painting a pattern. No audio hardware is required in the checks.
Read
spekkr.inputs.jsonfirst.titlelabels the grid.bpmandstepssize the bar.kitchooses the samples.swingandcountchange timing. Renders are offline.Out of scope
- A trademarked drum-machine model, or ripped commercial samples.
- A live speaker or MIDI device in the checks.
- Network or a sample marketplace in the checks.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Onsets and bar length
- A bar is
60 / bpm * 4seconds (4/4). A step is that length divided bysteps. fixtures/pattern-a.jsonat 120 bpm, 16 steps, swing off, rendered offline, has onsets (first sample of each hit above a threshold) within 2 ms of the listed step times, and a total length of one bar within 2 ms (or two bars if the fixture says so).- With
swingon, even steps (1-based steps 2, 4, …) are late by 16% of a step, within 2 ms.
Accept when: pattern A's onsets and length match at 120 and at 80 bpm, with swing off and on.
R2. UI and files
- A UI script paints pattern A onto a clear grid and reads it back as the same cells.
- Goldens: a clear grid, pattern A, the box kit's pads, and a playing head at step 5, buffer time frozen.
- One command renders, checks onsets, paints the grid, and writes the frames. No audio device. Samples are local.
Accept when: the read-back matches, both kits' pattern A onsets pass, 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
A fixture pattern renders an offline audio buffer whose onset times and bar length match the grid, within 2 ms, including a swing case. UI tests paint and read back the pattern. Samples are original or permissively licensed. No audio hardware and no trademarked model name.
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 a pattern, how the kits are licensed, and how to run the checks.
# Drum machine ## What this builds A drum sequencer you can jam with at once: a grid of steps, a few voices, a tempo, and a play control. The samples are original or permissively licensed, not a ripped commercial machine, and the product does not use a trademarked model number in its id or its name. A fixture pattern is rendered offline to a buffer; onset times and the bar length must match the grid. UI tests cover painting a pattern. No audio hardware is required in the checks. Read `spekkr.inputs.json` first. `title` labels the grid. `bpm` and `steps` size the bar. `kit` chooses the samples. `swing` and `count` change timing. Renders are offline. ## Out of scope - A trademarked drum-machine model, or ripped commercial samples. - A live speaker or MIDI device in the checks. - Network or a sample marketplace in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Onsets and bar length - A bar is `60 / bpm * 4` seconds (4/4). A step is that length divided by `steps`. - `fixtures/pattern-a.json` at 120 bpm, 16 steps, swing off, rendered offline, has onsets (first sample of each hit above a threshold) within 2 ms of the listed step times, and a total length of one bar within 2 ms (or two bars if the fixture says so). - With `swing` on, even steps (1-based steps 2, 4, …) are late by 16% of a step, within 2 ms. Accept when: pattern A's onsets and length match at 120 and at 80 bpm, with swing off and on. ### R2. UI and files - A UI script paints pattern A onto a clear grid and reads it back as the same cells. - Goldens: a clear grid, pattern A, the box kit's pads, and a playing head at step 5, buffer time frozen. - One command renders, checks onsets, paints the grid, and writes the frames. No audio device. Samples are local. Accept when: the read-back matches, both kits' pattern A onsets pass, 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 A fixture pattern renders an offline audio buffer whose onset times and bar length match the grid, within 2 ms, including a swing case. UI tests paint and read back the pattern. Samples are original or permissively licensed. No audio hardware and no trademarked model name. ## 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 a pattern, how the kits are licensed, and how to run the checks.
-
design.mdGrid timing, swing, and the fixture pattern's onsets.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.
Pattern A
Kick on 1 and 9, snare on 5 and 13, closed hat on every odd step, at 16 steps. Voices and the onset threshold are in
fixtures/pattern-a.json.Screenshot tolerance
8 levels, 98% of pixels. Timing is on the buffer.
Inputs
Key Label Default Notes titleTitle A small drum grid Shown above the sequencer. bpmTempo 120 From 60 to 200. Tests also use 80 and 140. stepsSteps per bar 16 8 or 16. swingSwing off A documented delay on even steps, 16% of a step, when on. countCount-in off One empty bar before the pattern, for a later jam. Tests usually leave this off. kitKit box Two shipped original sample kits, licensed in the repo. 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/pattern-a.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/grid.pngThe 16-step fixture pattern at 120 bpm, playhead on step 5. 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 fixture pattern renders an offline audio buffer whose onset times and bar length match the grid, within 2 ms, including a swing case. UI tests paint and read back the pattern. Samples are original or permissively licensed. No audio hardware and no trademarked model name.
# 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. ## Pattern A Kick on 1 and 9, snare on 5 and 13, closed hat on every odd step, at 16 steps. Voices and the onset threshold are in `fixtures/pattern-a.json`. ## Screenshot tolerance 8 levels, 98% of pixels. Timing is on the buffer. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A small drum grid | Shown above the sequencer. | | `bpm` | Tempo | 120 | From 60 to 200. Tests also use 80 and 140. | | `steps` | Steps per bar | 16 | 8 or 16. | | `swing` | Swing | off | A documented delay on even steps, 16% of a step, when on. | | `count` | Count-in | off | One empty bar before the pattern, for a later jam. Tests usually leave this off. | | `kit` | Kit | box | Two shipped original sample kits, licensed in the repo. | ## 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/pattern-a.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/grid.png` | The 16-step fixture pattern at 120 bpm, playhead on step 5. | ## 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 fixture pattern renders an offline audio buffer whose onset times and bar length match the grid, within 2 ms, including a swing case. UI tests paint and read back the pattern. Samples are original or permissively licensed. No audio hardware and no trademarked model name.
-
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. - Onsets and bar length (R1). Build what
R1. Onsets and bar lengthasks for, to the numbers indesign.md. In particular: A bar is `60 / bpm
- 4
seconds (4/4). A step is that length divided bysteps. Check: theR1. Onsets and bar length` acceptance checks pass.
- UI and files (R2). Build what
R2. UI and filesasks for, to the numbers indesign.md. In particular: A UI script paints pattern A onto a clear grid and reads it back as the same cells. Check: theR2. UI and filesacceptance checks pass. - Inputs (R3). Build what
R3. 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: theR3. Inputsacceptance checks pass. - Checks and report (R4). Build what
R4. Checks and reportasks for, to the numbers indesign.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: theR4. Checks and reportacceptance 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. **Onsets and bar length (R1).** Build what `R1. Onsets and bar length` asks for, to the numbers in `design.md`. In particular: A bar is `60 / bpm * 4` seconds (4/4). A step is that length divided by `steps`. Check: the `R1. Onsets and bar length` acceptance checks pass. 3. **UI and files (R2).** Build what `R2. UI and files` asks for, to the numbers in `design.md`. In particular: A UI script paints pattern A onto a clear grid and reads it back as the same cells. Check: the `R2. UI 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.
- 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
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that can write a wav file
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.