Lofi cafe

A small cafe scene with toggles and a bundled audio loop: play and pause are tested, and a golden screenshot, with no third-party stream.

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

Build this spec

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

Lofi cafe: heroLofi cafe: loop

What can I customize?

Room Two shipped scenes.

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.

    Lofi cafe

    What this builds

    A calm cafe scene you can sit with. Toggles change the weather and the light. A bundled audio loop plays and pauses from a control; there is no third-party stream, and a hook fails if one is contacted. The music and the art are original or permissively licensed, listed in a licence file. A golden screenshot is taken for a couple of scene states.

    Read spekkr.inputs.json first. title is on a sign. volume is the default. room chooses the scene. rain and lamplight are the toggles.

    Out of scope

    • A live radio or a commercial streaming service.
    • Network or a chat room in the checks.
    • A real cafe booking.

    Requirements

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

    R1. Scene toggles
    • Each combination of room, rain, and lamplight draws the documented layers. Goldens exist for window-day (rain off, lamps off), window-rain, and counter.
    • A toggle updates the scene without a reload.

    Accept when: the three (plus paused) frames match the goldens, and a toggle from day to rain matches the rain golden.

    R2. Audio and hooks
    • Play starts the bundled loop, at volume. Pause stops it. Tests use an offline or mocked element and assert that the local file was requested, and that play/pause changed a documented playing flag.
    • A fetch hook fails if a known stream or radio host is contacted.
    • The licence file lists the loop.

    Accept when: play and pause flip the flag, the requested src is the local loop, and the hook stays quiet.

    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

    Scene toggles have golden screenshots. Play and pause are tested against a bundled loop, not a third-party stream; a fetch hook fails otherwise. Licences for art and audio are shipped. 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 toggle the scene, how the loop is licensed, and how to run the checks.
    # Lofi cafe
    
    ## What this builds
    
    A calm cafe scene you can sit with. Toggles change the weather and the
    light. A bundled audio loop plays and pauses from a control; there is no
    third-party stream, and a hook fails if one is contacted. The music and
    the art are original or permissively licensed, listed in a licence file. A
    golden screenshot is taken for a couple of scene states.
    
    Read `spekkr.inputs.json` first. `title` is on a sign. `volume` is the
    default. `room` chooses the scene. `rain` and `lamplight` are the toggles.
    
    ## Out of scope
    
    - A live radio or a commercial streaming service.
    - Network or a chat room in the checks.
    - A real cafe booking.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Scene toggles
    
    - Each combination of room, rain, and lamplight draws the documented
      layers. Goldens exist for window-day (rain off, lamps off), window-rain,
      and counter.
    - A toggle updates the scene without a reload.
    
    Accept when: the three (plus paused) frames match the goldens, and a
    toggle from day to rain matches the rain golden.
    
    ### R2. Audio and hooks
    
    - Play starts the bundled loop, at `volume`. Pause stops it. Tests use an
      offline or mocked element and assert that the local file was requested,
      and that play/pause changed a documented playing flag.
    - A fetch hook fails if a known stream or radio host is contacted.
    - The licence file lists the loop.
    
    Accept when: play and pause flip the flag, the requested src is the local
    loop, and the hook stays quiet.
    
    ### 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
    
    Scene toggles have golden screenshots. Play and pause are tested against a
    bundled loop, not a third-party stream; a fetch hook fails otherwise.
    Licences for art and audio are shipped. 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 toggle the scene, how the loop is licensed, and how
      to run the checks.
    

    Open spec.md as plain text

  • design.md Scene layers, the bundled loop, and the no-stream rule.

    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.

    Loops

    audio/window-loop.wav and optional audio/rain.wav, licensed in LICENCE.md. Tests may use a short fixture loop of 4 seconds in place of a long one, listed in the same file.

    Screenshot tolerance

    8 levels, 98% of pixels.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA quiet tableShown on a sign in the scene.
    volumeDefault volume0.7From 0 to 1.
    rainRain on the windowonA visual and, if audio layers are on, a rain bed from a bundled loop.
    lamplightEvening lampsonA warmer light.
    roomRoomwindowTwo shipped scenes.

    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/table.pngA quiet table, rain at the window, the bundled loop playing at 0.7.

    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. Scene toggles have golden screenshots. Play and pause are tested against a bundled loop, not a third-party stream; a fetch hook fails otherwise. Licences for art and audio are shipped. 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.
    
    ## Loops
    
    `audio/window-loop.wav` and optional `audio/rain.wav`, licensed in
    `LICENCE.md`. Tests may use a short fixture loop of 4 seconds in place of
    a long one, listed in the same file.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A quiet table | Shown on a sign in the scene. |
    | `volume` | Default volume | 0.7 | From 0 to 1. |
    | `rain` | Rain on the window | on | A visual and, if audio layers are on, a rain bed from a bundled loop. |
    | `lamplight` | Evening lamps | on | A warmer light. |
    | `room` | Room | window | Two shipped scenes. |
    
    ## 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/table.png` | A quiet table, rain at the window, the bundled loop playing at 0.7. |
    
    
    ## 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. Scene toggles have golden screenshots. Play and pause are tested
    against a bundled loop, not a third-party stream; a fetch hook fails
    otherwise. Licences for art and audio are shipped. No network is required.
    

    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 toggles (R1). Build what R1. Scene toggles asks for, to the numbers in design.md. In particular: Each combination of room, rain, and lamplight draws the documented layers. Goldens exist for window-day (rain off, lamps off), window-rain, and counter. Check: the R1. Scene toggles acceptance checks pass.
    3. Audio and hooks (R2). Build what R2. Audio and hooks asks for, to the numbers in design.md. In particular: Play starts the bundled loop, at volume. Pause stops it. Tests use an offline or mocked element and assert that the local file was requested, and that play/pause changed a documented playing flag. Check: the R2. Audio and hooks 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 toggles (R1).** Build what `R1. Scene toggles` asks for, to the
    numbers in `design.md`. In particular: Each combination of room, rain, and
    lamplight draws the documented layers. Goldens exist for window-day (rain
    off, lamps off), window-rain, and counter.
       Check: the `R1. Scene toggles` acceptance checks pass.
    
    3. **Audio and hooks (R2).** Build what `R2. Audio and hooks` asks for, to
    the numbers in `design.md`. In particular: Play starts the bundled loop,
    at `volume`. Pause stops it. Tests use an offline or mocked element and
    assert that the local file was requested, and that play/pause changed a
    documented playing flag.
       Check: the `R2. Audio and hooks` 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/Fraunces.ttf Fraunces variable typeface for the reference preview.
  • reference/fonts/Fraunces-Italic.ttf Fraunces italic variable typeface 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.115 Nov 2026Add the cat, lamp, rainy city, and booth interior, and 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.