# Build Drum machine You were asked to build the spec `lume/drum-machine`, version 0.2.2, from Spekkr. A tight in-browser sequencer: a fixture pattern renders a buffer whose onsets and bar length match the grid, plus UI pattern tests. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/lume/drum-machine/start.md`, before you go on. Published by lume, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `drum-machine`, inside the project you are working in. ```sh mkdir -p drum-machine && curl -fsSL https://spekkr.com/lume/drum-machine/bundle.tar.gz | tar -xz -C drum-machine ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/lume/drum-machine/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `lume/drum-machine` and the person's choices. ## 2. Record the person's choices Write `drum-machine/spekkr.inputs.json`. With every default it is: ```json { "spec": "lume/drum-machine", "version": "0.2.2", "inputs": { "bpm": "120", "count": false, "kit": "box", "steps": "16", "swing": false, "title": "A small drum grid" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `title`, Title: any text. - `bpm`, Tempo: any text. - `steps`, Steps per bar: any text. - `swing`, Swing: `on` or `off`, written `true` or `false`. - `count`, Count-in: `on` or `off`, written `true` or `false`. - `kit`, Kit: one of `box`, `tight`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `drum-machine`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements and acceptance checks. - `design.md`: Grid timing, swing, and the fixture pattern's onsets. - `tasks.md`: Build tasks in order, each with a check. - `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/GeistMono.ttf`: Geist Mono variable typeface for the reference preview. - `reference/fonts/Fraunces.ttf`: Fraunces variable typeface for the reference preview. - `reference/fonts/Fraunces-Italic.ttf`: Fraunces italic variable typeface for the reference preview.