Poolside radio

A retro poolside scene with visual-regression goldens, and a bundled playlist whose first fixture track actually starts.

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/poolside-radio
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/lume/poolside-radio/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?

Poolside radio: heroPoolside radio: duskPoolside radio: objectPoolside radio: loop

What can I customize?

Playlist Bundled, licensed tracks. No live stream.

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.md Requirements and acceptance checks.

    Poolside radio

    What this builds

    A still, retro poolside scene with a radio you can start. The playlist is bundled and licensed in the repo. Tests check the scene by visual regression, and they assert that a fixture track actually starts (a playing flag and a local src). A hook fails if a stream host is contacted. The art is original.

    Read spekkr.inputs.json first. title is on the set. track is the starting index. playlist chooses the bundle. water and sun change the picture. Water may be frozen in checks.

    Out of scope

    • A live radio or a commercial stream.
    • Network in the checks.
    • A real pool booking.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. Scene and track
    • The default scene, water frozen, sun on, matches the scene golden.
    • Play starts playlist[track] as a local file, sets a playing flag, and the playing frame matches.
    • A next-track control advances the index, modulo the list, and starts that file.

    Accept when: the goldens match, the src is local, and next-track advances as listed.

    R2. Files
    • A licence file lists every track. A fetch hook fails if a stream host is contacted.
    • One command compares the frames, starts the track, hooks, and writes sun-off as well. No network.

    Accept when: the hook stays quiet, licences are present, and all four frames match.

    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

    Visual regression covers the scene. A bundled playlist track actually starts (local src, playing flag). Next-track advances. A fetch hook fails if a live stream is contacted. Licences are shipped. 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 start the radio, how tracks are licensed, and how to run the checks.
    # Poolside radio
    
    ## What this builds
    
    A still, retro poolside scene with a radio you can start. The playlist is
    bundled and licensed in the repo. Tests check the scene by visual
    regression, and they assert that a fixture track actually starts (a
    playing flag and a local src). A hook fails if a stream host is contacted.
    The art is original.
    
    Read `spekkr.inputs.json` first. `title` is on the set. `track` is the
    starting index. `playlist` chooses the bundle. `water` and `sun` change
    the picture. Water may be frozen in checks.
    
    ## Out of scope
    
    - A live radio or a commercial stream.
    - Network in the checks.
    - A real pool booking.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Scene and track
    
    - The default scene, water frozen, sun on, matches the `scene` golden.
    - Play starts `playlist[track]` as a local file, sets a playing flag, and
      the `playing` frame matches.
    - A next-track control advances the index, modulo the list, and starts
      that file.
    
    Accept when: the goldens match, the src is local, and next-track advances
    as listed.
    
    ### R2. Files
    
    - A licence file lists every track. A fetch hook fails if a stream host is
      contacted.
    - One command compares the frames, starts the track, hooks, and writes
      sun-off as well. No network.
    
    Accept when: the hook stays quiet, licences are present, and all four
    frames match.
    
    ### 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
    
    Visual regression covers the scene. A bundled playlist track actually
    starts (local src, playing flag). Next-track advances. A fetch hook fails
    if a live stream is contacted. Licences are shipped. 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 start the radio, how tracks are licensed, and how
      to run the checks.
    

    Open spec.md as plain text

  • design.md The bundled playlist, scene goldens, and the start-track check.

    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.

    Afternoon playlist

    At least two short fixture tracks, licensed in LICENCE.md. The short playlist is the first two.

    Screenshot tolerance

    8 levels, 98% of pixels, water frozen at t = 0.

    Inputs

    KeyLabelDefaultNotes
    titleTitleBy the waterShown on a small sign or a set badge.
    trackStarting track0An index into the bundled playlist.
    waterAnimate the wateronA short loop. Tests may freeze it at t = 0.
    sunLate-afternoon sunonA warmer wash.
    playlistPlaylistafternoonBundled, licensed tracks. No live stream.

    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.

    FixtureRole
    LICENCE.mdA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA 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.

    FileWhat it shows
    shots/deck.pngBy the water, track 0 of the bundled playlist, sun on the pool.

    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. Visual regression covers the scene. A bundled playlist track actually starts (local src, playing flag). Next-track advances. A fetch hook fails if a live stream is contacted. Licences are shipped. 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.
    
    ## Afternoon playlist
    
    At least two short fixture tracks, licensed in `LICENCE.md`. The short
    playlist is the first two.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels, water frozen at t = 0.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | By the water | Shown on a small sign or a set badge. |
    | `track` | Starting track | 0 | An index into the bundled playlist. |
    | `water` | Animate the water | on | A short loop. Tests may freeze it at t = 0. |
    | `sun` | Late-afternoon sun | on | A warmer wash. |
    | `playlist` | Playlist | afternoon | Bundled, licensed tracks. No live stream. |
    
    ## 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 |
    | --- | --- |
    | `LICENCE.md` | 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/deck.png` | By the water, track 0 of the bundled playlist, sun on the pool. |
    
    
    ## 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. Visual regression covers the scene. A bundled playlist track actually
    starts (local src, playing flag). Next-track advances. A fetch hook fails
    if a live stream is contacted. Licences are shipped. No network.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    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. Scene and track (R1). Build what R1. Scene and track asks for, to the numbers in design.md. In particular: The default scene, water frozen, sun on, matches the scene golden. Check: the R1. Scene and track acceptance checks pass.
    3. Files (R2). Build what R2. Files asks for, to the numbers in design.md. In particular: A licence file lists every track. A fetch hook fails if a stream host is contacted. Check: the R2. 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.
    # 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. **Scene and track (R1).** Build what `R1. Scene and track` asks for, to
    the numbers in `design.md`. In particular: The default scene, water
    frozen, sun on, matches the `scene` golden.
       Check: the `R1. Scene and track` acceptance checks pass.
    
    3. **Files (R2).** Build what `R2. Files` asks for, to the numbers in
    `design.md`. In particular: A licence file lists every track. A fetch hook
    fails if a stream host is contacted.
       Check: the `R2. 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.
    

    Open tasks.md as plain text

  • 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/InstrumentSerif.ttf Instrument Serif for the reference preview.
  • reference/fonts/InstrumentSerif-Italic.ttf Instrument Serif italic for the reference preview.

Is it for me?

Platforms
web
Tools
TypeScript

What does it need?

Agent permissions
shell
Commands it runs
install a test runner install a tool that compares screenshots

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.