Weekend arcade
A tiny catch-and-avoid game with juicy motion, a seeded run, collision and score tests, and a golden play frame.
This is a browser game spec on Spekkr, published by nova. 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
nova/weekend-arcade- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/weekend-arcade/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 nova.
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.Weekend arcade
What this builds
A short arcade game. Pieces fall. The person moves a paddle or a small catcher along the bottom. Catching the right kind scores; catching the wrong kind, or missing a required one, costs a life. Motion is juicy but deterministic under a seed. The shapes, the feel and the scoring are original. A run is finishable in a minute and readable in a still.
Read
spekkr.inputs.jsonfirst.titleis the attract heading.livesis the starting count.pacesets the spawn rate.juiceandshakeadd feel; tests settle them before comparing frames.Out of scope
- A long campaign or meta-progression.
- Network or a public scoreboard in the checks.
- A second stick or a virtual-reality mode.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Collision and score
- The catcher is a 80 by 16 px rounded bar. A piece is a 24 px square. A catch is an overlap of their axis-aligned boxes.
- A
goodpiece scored on catch adds 10, and 1 to a combo that multiplies the next good catch, cap 8. - A
badpiece on catch, or agoodpiece that passes the bottom, costs one life and resets the combo.
Accept when: the collision fixtures in
design.mdreport catch or miss as listed, and the score trail of the seeded run matches the file.R2. A seeded run
- Seed 11,
standardpace, 3 lives, produces the spawn tape infixtures/arcade-seed-11.json. - A scripted catcher path in that file plays through 20 seconds and ends with the score and lives in the file.
- The same seed and path replay bit-identically.
Accept when: two runs hash the same score trail, and the ending score and lives match the file.
R3. Frames and files
- Four frames from the seed-11 run, animations settled: attract, a catch, a near-miss, and a busy field at t = 16 s.
- One command runs collision, seed, and replay tests, and writes the frames. No network.
Accept when: the command passes at every pace, and the frames match the goldens.
R4. 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.
Verification
Collision and score tests cover a catch, a miss, a corner touch, and combo reset. A seeded 20-second run with a scripted catcher path is replayable and matches a score trail. A golden gameplay frame is taken with motion juice settled. 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 play, how to pin a seed, and how to run the checks.
# Weekend arcade ## What this builds A short arcade game. Pieces fall. The person moves a paddle or a small catcher along the bottom. Catching the right kind scores; catching the wrong kind, or missing a required one, costs a life. Motion is juicy but deterministic under a seed. The shapes, the feel and the scoring are original. A run is finishable in a minute and readable in a still. Read `spekkr.inputs.json` first. `title` is the attract heading. `lives` is the starting count. `pace` sets the spawn rate. `juice` and `shake` add feel; tests settle them before comparing frames. ## Out of scope - A long campaign or meta-progression. - Network or a public scoreboard in the checks. - A second stick or a virtual-reality mode. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Collision and score - The catcher is a 80 by 16 px rounded bar. A piece is a 24 px square. A catch is an overlap of their axis-aligned boxes. - A `good` piece scored on catch adds 10, and 1 to a combo that multiplies the next good catch, cap 8. - A `bad` piece on catch, or a `good` piece that passes the bottom, costs one life and resets the combo. Accept when: the collision fixtures in `design.md` report catch or miss as listed, and the score trail of the seeded run matches the file. ### R2. A seeded run - Seed 11, `standard` pace, 3 lives, produces the spawn tape in `fixtures/arcade-seed-11.json`. - A scripted catcher path in that file plays through 20 seconds and ends with the score and lives in the file. - The same seed and path replay bit-identically. Accept when: two runs hash the same score trail, and the ending score and lives match the file. ### R3. Frames and files - Four frames from the seed-11 run, animations settled: attract, a catch, a near-miss, and a busy field at t = 16 s. - One command runs collision, seed, and replay tests, and writes the frames. No network. Accept when: the command passes at every pace, and the frames match the goldens. ### R4. 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. ## Verification Collision and score tests cover a catch, a miss, a corner touch, and combo reset. A seeded 20-second run with a scripted catcher path is replayable and matches a score trail. A golden gameplay frame is taken with motion juice settled. 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 play, how to pin a seed, and how to run the checks.
-
design.mdCollision boxes, spawn rates, and the seeded 20-second run.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.
Collision fixtures
Cases in
fixtures/arcade-hits.json: a piece centred on the bar is a catch; a piece 1 px past the bar's end is a miss; a piece that touches a corner is a catch.Spawn rate
At t = 0, pieces per second are 1.0, 1.6, 2.4 for easy, standard, busy. Every 8 seconds the rate is multiplied by 1.15.
Seed 11
The tape file is the authority for spawns, the catcher path, the score trail, and the ending. Goldens are 1600 by 1000, 8 levels, 98% of pixels, juice settled.
Inputs
Key Label Default Notes titleTitle One more catch Shown on the attract screen. livesLives 3 From 1 to 6. juiceMotion juice on A short squash and a flash on a catch or a hit. Tests may jump to the settled frame. shakeScreen shake on A 6-frame shake on a hit, seeded so goldens are stable. pacePace standard How many falling pieces per second at the start. 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/arcade-hits.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/arcade-seed-11.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/catch.pngMid-game, 2 860 points, one more catch on the paddle. 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.
- Collision and score tests cover a catch, a miss, a corner touch, and combo reset. A seeded 20-second run with a scripted catcher path is replayable and matches a score trail. A golden gameplay frame is taken with motion juice settled. 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. ## Collision fixtures Cases in `fixtures/arcade-hits.json`: a piece centred on the bar is a catch; a piece 1 px past the bar's end is a miss; a piece that touches a corner is a catch. ## Spawn rate At t = 0, pieces per second are 1.0, 1.6, 2.4 for easy, standard, busy. Every 8 seconds the rate is multiplied by 1.15. ## Seed 11 The tape file is the authority for spawns, the catcher path, the score trail, and the ending. Goldens are 1600 by 1000, 8 levels, 98% of pixels, juice settled. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | One more catch | Shown on the attract screen. | | `lives` | Lives | 3 | From 1 to 6. | | `juice` | Motion juice | on | A short squash and a flash on a catch or a hit. Tests may jump to the settled frame. | | `shake` | Screen shake | on | A 6-frame shake on a hit, seeded so goldens are stable. | | `pace` | Pace | standard | How many falling pieces per second at the start. | ## 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/arcade-hits.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/arcade-seed-11.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/catch.png` | Mid-game, 2 860 points, one more catch on the paddle. | ## 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. Collision and score tests cover a catch, a miss, a corner touch, and combo reset. A seeded 20-second run with a scripted catcher path is replayable and matches a score trail. A golden gameplay frame is taken with motion juice settled. No network.
-
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. - Collision and score (R1). Build what
R1. Collision and scoreasks for, to the numbers indesign.md. In particular: The catcher is a 80 by 16 px rounded bar. A piece is a 24 px square. A catch is an overlap of their axis-aligned boxes. Check: theR1. Collision and scoreacceptance checks pass. - A seeded run (R2). Build what
R2. A seeded runasks for, to the numbers indesign.md. In particular: Seed 11,standardpace, 3 lives, produces the spawn tape infixtures/arcade-seed-11.json. Check: theR2. A seeded runacceptance checks pass. - Frames and files (R3). Build what
R3. Frames and filesasks for, to the numbers indesign.md. In particular: Four frames from the seed-11 run, animations settled: attract, a catch, a near-miss, and a busy field at t = 16 s. Check: theR3. Frames and filesacceptance checks pass. - Inputs (R4). Build what
R4. 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: theR4. Inputsacceptance 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. **Collision and score (R1).** Build what `R1. Collision and score` asks for, to the numbers in `design.md`. In particular: The catcher is a 80 by 16 px rounded bar. A piece is a 24 px square. A catch is an overlap of their axis-aligned boxes. Check: the `R1. Collision and score` acceptance checks pass. 3. **A seeded run (R2).** Build what `R2. A seeded run` asks for, to the numbers in `design.md`. In particular: Seed 11, `standard` pace, 3 lives, produces the spawn tape in `fixtures/arcade-seed-11.json`. Check: the `R2. A seeded run` acceptance checks pass. 4. **Frames and files (R3).** Build what `R3. Frames and files` asks for, to the numbers in `design.md`. In particular: Four frames from the seed-11 run, animations settled: attract, a catch, a near-miss, and a busy field at t = 16 s. Check: the `R3. Frames and files` acceptance checks pass. 5. **Inputs (R4).** Build what `R4. 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 `R4. Inputs` 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/Unbounded.ttfUnbounded variable typeface for the reference preview.
Is it for me?
- Kind
- browser game
- 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.