Window swap
A swap of window views from fixture clips with documented locations, and upload hooks tested with files, not a live camera.
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/window-swap- Version
- 0.2.2
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/window-swap/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.Window swap
What this builds
A quiet page that shows a window view, then swaps to another. The views are fixture clips with documented locations, not a live camera network. An upload hook can be tested with a file, including a refusal of an oversized or typeless file, without opening a camera. The clips are original or permissively licensed.
Read
spekkr.inputs.jsonfirst.titlesits under the frame.intervalis the swap time; tests inject the clock.setchooses the clips.captionandaudiochange the chrome.Out of scope
- A live camera network, or other people's private windows.
- A webcam in the checks.
- Network to a public swap service in the checks.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Fixture clips and swap
- The sample set lists clips, each with a file, a location string, and a duration. At t = 0 the first clip is shown; after
intervalseconds of injected time, the next is shown, wrapping the list. - The caption, if on, is the location string of the current clip.
- A fetch hook fails if a camera or a remote clip host is contacted.
Accept when: the first and second clips and captions match the file at t = 0 and t = interval, and the hook stays quiet.
R2. Upload hook and frames
- An upload endpoint (in-process) accepts a fixture file of an allowed type and size, and refuses a file that is too large or of a disallowed type, with a message.
- There is no getUserMedia path in the checks. Goldens: the first window, after a swap, a caption, and an upload preview of the accepted fixture.
- One command runs the swap, the hook, the upload cases, and writes the frames. The clock is injected. No camera and no network.
Accept when: accept and refuse cases match, 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 clips are served with documented locations and swap on an injected clock. Upload and moderation hooks are tested with files, not a live camera. A fetch hook fails if a remote camera host is contacted. Golden frames are taken. Licences are shipped.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how the clips are licensed, how to test an upload, and how to run the checks.
# Window swap ## What this builds A quiet page that shows a window view, then swaps to another. The views are fixture clips with documented locations, not a live camera network. An upload hook can be tested with a file, including a refusal of an oversized or typeless file, without opening a camera. The clips are original or permissively licensed. Read `spekkr.inputs.json` first. `title` sits under the frame. `interval` is the swap time; tests inject the clock. `set` chooses the clips. `caption` and `audio` change the chrome. ## Out of scope - A live camera network, or other people's private windows. - A webcam in the checks. - Network to a public swap service in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Fixture clips and swap - The sample set lists clips, each with a file, a location string, and a duration. At t = 0 the first clip is shown; after `interval` seconds of injected time, the next is shown, wrapping the list. - The caption, if on, is the location string of the current clip. - A fetch hook fails if a camera or a remote clip host is contacted. Accept when: the first and second clips and captions match the file at t = 0 and t = interval, and the hook stays quiet. ### R2. Upload hook and frames - An upload endpoint (in-process) accepts a fixture file of an allowed type and size, and refuses a file that is too large or of a disallowed type, with a message. - There is no getUserMedia path in the checks. Goldens: the first window, after a swap, a caption, and an upload preview of the accepted fixture. - One command runs the swap, the hook, the upload cases, and writes the frames. The clock is injected. No camera and no network. Accept when: accept and refuse cases match, 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 clips are served with documented locations and swap on an injected clock. Upload and moderation hooks are tested with files, not a live camera. A fetch hook fails if a remote camera host is contacted. Golden frames are taken. Licences are shipped. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how the clips are licensed, how to test an upload, and how to run the checks.
-
design.mdFixture clips, swap timing, and the file-based upload hook.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 three clips, locations in
fixtures/windows.json, licensed inLICENCE.md. Allowed upload types:mp4,webm,jpg,png. Max size 8 MB, as in the file.Screenshot tolerance
8 levels, 98% of pixels (12 levels if a video decoder is not bit-exact).
Inputs
Key Label Default Notes titleTitle Someone else's window Shown under the frame. intervalSwap every, seconds 12 From 4 to 60. Tests inject the clock. captionShow a location caption on A short place name from the fixture. audioPlay a low room sound off A bundled loop, optional. Tests may leave this off. setClip set sample Shipped clips with documented locations. No live camera. 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.mdA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/windows.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/lisbon.pngSomeone else's window, Lisbon at dusk, interval 12 seconds. 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 clips are served with documented locations and swap on an injected clock. Upload and moderation hooks are tested with files, not a live camera. A fetch hook fails if a remote camera host is contacted. Golden frames are taken. Licences are shipped.
# 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 three clips, locations in `fixtures/windows.json`, licensed in `LICENCE.md`. Allowed upload types: `mp4`, `webm`, `jpg`, `png`. Max size 8 MB, as in the file. ## Screenshot tolerance 8 levels, 98% of pixels (12 levels if a video decoder is not bit-exact). ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Someone else's window | Shown under the frame. | | `interval` | Swap every, seconds | 12 | From 4 to 60. Tests inject the clock. | | `caption` | Show a location caption | on | A short place name from the fixture. | | `audio` | Play a low room sound | off | A bundled loop, optional. Tests may leave this off. | | `set` | Clip set | sample | Shipped clips with documented locations. No live camera. | ## 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. | | `fixtures/windows.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/lisbon.png` | Someone else's window, Lisbon at dusk, interval 12 seconds. | ## 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 clips are served with documented locations and swap on an injected clock. Upload and moderation hooks are tested with files, not a live camera. A fetch hook fails if a remote camera host is contacted. Golden frames are taken. Licences are shipped.
-
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. - Fixture clips and swap (R1). Build what
R1. Fixture clips and swapasks for, to the numbers indesign.md. In particular: The sample set lists clips, each with a file, a location string, and a duration. At t = 0 the first clip is shown; afterintervalseconds of injected time, the next is shown, wrapping the list. Check: theR1. Fixture clips and swapacceptance checks pass. - Upload hook and frames (R2). Build what
R2. Upload hook and framesasks for, to the numbers indesign.md. In particular: An upload endpoint (in-process) accepts a fixture file of an allowed type and size, and refuses a file that is too large or of a disallowed type, with a message. Check: theR2. Upload hook and framesacceptance 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. **Fixture clips and swap (R1).** Build what `R1. Fixture clips and swap` asks for, to the numbers in `design.md`. In particular: The sample set lists clips, each with a file, a location string, and a duration. At t = 0 the first clip is shown; after `interval` seconds of injected time, the next is shown, wrapping the list. Check: the `R1. Fixture clips and swap` acceptance checks pass. 3. **Upload hook and frames (R2).** Build what `R2. Upload hook and frames` asks for, to the numbers in `design.md`. In particular: An upload endpoint (in-process) accepts a fixture file of an allowed type and size, and refuses a file that is too large or of a disallowed type, with a message. Check: the `R2. Upload hook and frames` 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/InstrumentSerif.ttfInstrument Serif for the reference preview. -
reference/fonts/InstrumentSerif-Italic.ttfInstrument Serif italic 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 runnerinstall 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.