Station melody
A music box of station jingles: fixture melodies play in documented order and length, with UI selection tests and licensed audio.
This is a small site 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/station-melody- Version
- 0.2.2
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/station-melody/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.Station melody
What this builds
A small box of short station-like melodies, each a place in a made-up network. Selecting one plays a bundled file. Tests assert the play order and the length of fixture melodies, and they cover the selection UI. Audio is original or permissively licensed, listed in a licence file. No live radio network is used.
Read
spekkr.inputs.jsonfirst.titlelabels the list.volumeis the default.setchooses the bundle.loopandlabelschange play and chrome.Out of scope
- A live transit authority's marks, or a commercial jingle pack without a licence.
- A live radio stream in the checks.
- Network in the checks.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Order and length
- The sample set's play-all order is the list in
fixtures/melodies.json. Each file's duration matches the listed length within 50 ms. - A play-all script starts them in that order, with no overlap unless
loopis on (loop is off for this script). - A licence file lists every track.
Accept when: order and durations match, and the licence file is present.
R2. UI and files
- Selecting a named melody sets it as current and starts it. A stop control stops it. Tests assert a playing flag and a local src.
- A fetch hook fails if a radio host is contacted. Goldens: the list, a selected item, a playing state, and the tiny set.
- One command runs durations, the script, the UI, the hook, and writes the frames. No audio device required beyond an offline or mocked element.
Accept when: the hook stays quiet, and the four 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
Fixture melodies play in documented order and length, within 50 ms. UI selection starts a local file. Bundled audio is licensed in the repo. A fetch hook fails if a live radio host is contacted. No network is required.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to pick a melody, how the files are licensed, and how to run the checks.
# Station melody ## What this builds A small box of short station-like melodies, each a place in a made-up network. Selecting one plays a bundled file. Tests assert the play order and the length of fixture melodies, and they cover the selection UI. Audio is original or permissively licensed, listed in a licence file. No live radio network is used. Read `spekkr.inputs.json` first. `title` labels the list. `volume` is the default. `set` chooses the bundle. `loop` and `labels` change play and chrome. ## Out of scope - A live transit authority's marks, or a commercial jingle pack without a licence. - A live radio stream in the checks. - Network in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Order and length - The sample set's play-all order is the list in `fixtures/melodies.json`. Each file's duration matches the listed length within 50 ms. - A play-all script starts them in that order, with no overlap unless `loop` is on (loop is off for this script). - A licence file lists every track. Accept when: order and durations match, and the licence file is present. ### R2. UI and files - Selecting a named melody sets it as current and starts it. A stop control stops it. Tests assert a playing flag and a local src. - A fetch hook fails if a radio host is contacted. Goldens: the list, a selected item, a playing state, and the tiny set. - One command runs durations, the script, the UI, the hook, and writes the frames. No audio device required beyond an offline or mocked element. Accept when: the hook stays quiet, and the four 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 Fixture melodies play in documented order and length, within 50 ms. UI selection starts a local file. Bundled audio is licensed in the repo. A fetch hook fails if a live radio host is contacted. No network is required. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to pick a melody, how the files are licensed, and how to run the checks.
-
design.mdFixture melody order, durations, and licensed bundled audio.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.
Sample set
At least five short fixture melodies, 2–8 seconds each, in
sets/sample/, listed with durations in the file. Tiny is the first two.Screenshot tolerance
8 levels, 98% of pixels.
Inputs
Key Label Default Notes titleTitle A little box of places Shown above the list. volumeVolume 0.8 From 0 to 1. loopLoop a melody off If on, a selected melody repeats until stopped. labelsShow place names on A caption next to each melody. setSet sample Bundled, licensed short melodies. No live radio. 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/melodies.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/box.pngThe little box of places, harbour phrase first, volume 0.8. 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 melodies play in documented order and length, within 50 ms. UI selection starts a local file. Bundled audio is licensed in the repo. A fetch hook fails if a live radio host is contacted. No network is required.
# 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. ## Sample set At least five short fixture melodies, 2–8 seconds each, in `sets/sample/`, listed with durations in the file. Tiny is the first two. ## Screenshot tolerance 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A little box of places | Shown above the list. | | `volume` | Volume | 0.8 | From 0 to 1. | | `loop` | Loop a melody | off | If on, a selected melody repeats until stopped. | | `labels` | Show place names | on | A caption next to each melody. | | `set` | Set | sample | Bundled, licensed short melodies. No live radio. | ## 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/melodies.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/box.png` | The little box of places, harbour phrase first, volume 0.8. | ## 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 melodies play in documented order and length, within 50 ms. UI selection starts a local file. Bundled audio is licensed in the repo. A fetch hook fails if a live radio host is contacted. No network is required.
-
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. - Order and length (R1). Build what
R1. Order and lengthasks for, to the numbers indesign.md. In particular: The sample set's play-all order is the list infixtures/melodies.json. Each file's duration matches the listed length within 50 ms. Check: theR1. Order and lengthacceptance checks pass. - UI and files (R2). Build what
R2. UI and filesasks for, to the numbers indesign.md. In particular: Selecting a named melody sets it as current and starts it. A stop control stops it. Tests assert a playing flag and a local src. 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. **Order and length (R1).** Build what `R1. Order and length` asks for, to the numbers in `design.md`. In particular: The sample set's play-all order is the list in `fixtures/melodies.json`. Each file's duration matches the listed length within 50 ms. Check: the `R1. Order and 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: Selecting a named melody sets it as current and starts it. A stop control stops it. Tests assert a playing flag and a local src. 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/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
- small site
- Platforms
- web
- Tools
- TypeScript
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runner
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.