Seven minute

A short workout timer: exercise order and durations are checked on a fake clock, with a golden mid-routine frame.

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

Build this spec

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

Seven minute: heroSeven minute: loop

What can I customize?

Routine classic is 12 moves, 30 seconds each, 10 seconds of rest. short is 4 moves, for quicker checks.

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.

    Seven minute

    What this builds

    A timer for a short, bodyweight routine. The moves, the order, and the durations are a file. An injectable clock drives the session. A golden mid-routine frame is taken. The routine is original in wording, even when it covers familiar moves. No sensor and no camera are required.

    Read spekkr.inputs.json first. title is at the start. prepare is a lead-in. routine chooses the list. beep and hold change cues and pause. The clock is injectable.

    Out of scope

    • A camera that judges form, or a wearable sensor.
    • A paid trainer catalogue.
    • Network or an account in the checks.

    Requirements

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

    R1. Order and durations
    • The classic routine is the 12 moves and the 30/10 timings in fixtures/routine-classic.json. Short is the first 4 moves with the same timings.
    • At injected times listed in the file, the current move and whether it is work or rest match the file, including the prepare window.
    • A pause, if on, freezes the remaining time until resumed.

    Accept when: every listed instant matches the move and phase, and a pause holds the remaining time.

    R2. Frames and files
    • Goldens: the start (prepare or first move), a mid-move, a rest, and a done screen.
    • One command runs the clock table, the pause, a mocked beep request, and writes the frames. No network and no sensors.

    Accept when: the command passes for both routines, 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

    Exercise order and durations are tested with a fake clock against a fixture table, including rest and a pause. A golden mid-routine screenshot is checked. Audio may be mocked. No camera, no sensor, and 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 routine, how to add a move, and how to run the checks.
    # Seven minute
    
    ## What this builds
    
    A timer for a short, bodyweight routine. The moves, the order, and the
    durations are a file. An injectable clock drives the session. A golden
    mid-routine frame is taken. The routine is original in wording, even when
    it covers familiar moves. No sensor and no camera are required.
    
    Read `spekkr.inputs.json` first. `title` is at the start. `prepare` is a
    lead-in. `routine` chooses the list. `beep` and `hold` change cues and
    pause. The clock is injectable.
    
    ## Out of scope
    
    - A camera that judges form, or a wearable sensor.
    - A paid trainer catalogue.
    - Network or an account in the checks.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Order and durations
    
    - The classic routine is the 12 moves and the 30/10 timings in
      `fixtures/routine-classic.json`. Short is the first 4 moves with the
      same timings.
    - At injected times listed in the file, the current move and whether it is
      work or rest match the file, including the prepare window.
    - A pause, if on, freezes the remaining time until resumed.
    
    Accept when: every listed instant matches the move and phase, and a pause
    holds the remaining time.
    
    ### R2. Frames and files
    
    - Goldens: the start (prepare or first move), a mid-move, a rest, and a
      done screen.
    - One command runs the clock table, the pause, a mocked beep request, and
      writes the frames. No network and no sensors.
    
    Accept when: the command passes for both routines, 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
    
    Exercise order and durations are tested with a fake clock against a
    fixture table, including rest and a pause. A golden mid-routine screenshot
    is checked. Audio may be mocked. No camera, no sensor, and 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 routine, how to add a move, and how to
      run the checks.
    

    Open spec.md as plain text

  • design.md Routine order, durations on a fake clock, and the mid-routine golden.

    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.

    Classic timings

    Prepare prepare seconds, then 12 cycles of 30 s work and 10 s rest, except there is no rest after the last move. The file is the authority for names and for the mid-move screenshot's time (start of move 6).

    Screenshot tolerance

    8 levels, 98% of pixels. The on-screen remaining time must also match the injected clock.

    Inputs

    KeyLabelDefaultNotes
    titleTitleSeven minutesShown at the start.
    preparePrepare, seconds5A countdown before the first move, from 0 to 10.
    beepBeep on a changeonTests may mock audio and only assert that a beep was requested.
    holdAllow a pauseonA control pauses the injected clock's effect on the routine.
    routineRoutineclassicclassic is 12 moves, 30 seconds each, 10 seconds of rest. short is 4 moves, for quicker checks.

    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
    fixtures/routine-classic.jsonA 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/squat.pngTwenty-two seconds into squat, after a five-second prepare, on a fake clock.

    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. Exercise order and durations are tested with a fake clock against a fixture table, including rest and a pause. A golden mid-routine screenshot is checked. Audio may be mocked. No camera, no sensor, and 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.
    
    ## Classic timings
    
    Prepare `prepare` seconds, then 12 cycles of 30 s work and 10 s rest,
    except there is no rest after the last move. The file is the authority for
    names and for the mid-move screenshot's time (start of move 6).
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. The on-screen remaining time must also match the
    injected clock.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | Seven minutes | Shown at the start. |
    | `prepare` | Prepare, seconds | 5 | A countdown before the first move, from 0 to 10. |
    | `beep` | Beep on a change | on | Tests may mock audio and only assert that a beep was requested. |
    | `hold` | Allow a pause | on | A control pauses the injected clock's effect on the routine. |
    | `routine` | Routine | classic | classic is 12 moves, 30 seconds each, 10 seconds of rest. short is 4 moves, for quicker checks. |
    
    ## 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/routine-classic.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/squat.png` | Twenty-two seconds into squat, after a five-second prepare, on a fake clock. |
    
    
    ## 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. Exercise order and durations are tested with a fake clock against a
    fixture table, including rest and a pause. A golden mid-routine screenshot
    is checked. Audio may be mocked. No camera, no sensor, and 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. Order and durations (R1). Build what R1. Order and durations asks for, to the numbers in design.md. In particular: The classic routine is the 12 moves and the 30/10 timings in fixtures/routine-classic.json. Short is the first 4 moves with the same timings. Check: the R1. Order and durations acceptance checks pass.
    3. Frames and files (R2). Build what R2. Frames and files asks for, to the numbers in design.md. In particular: Goldens: the start (prepare or first move), a mid-move, a rest, and a done screen. Check: the R2. Frames 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.
    # 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 durations (R1).** Build what `R1. Order and durations` asks
    for, to the numbers in `design.md`. In particular: The classic routine is
    the 12 moves and the 30/10 timings in `fixtures/routine-classic.json`.
    Short is the first 4 moves with the same timings.
       Check: the `R1. Order and durations` acceptance checks pass.
    
    3. **Frames and files (R2).** Build what `R2. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: the start (prepare
    or first move), a mid-move, a rest, and a done screen.
       Check: the `R2. Frames 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.
    

    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/Unbounded.ttf Unbounded 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.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.