QR fps

A tiny original first-person loop that packs into a scannable code, decodes, boots, and passes a scripted walkthrough.

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/qr-fps
Version
0.2.2
Published by
nova
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/nova/qr-fps/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?

QR fps: heroQR fps: loop

What can I customize?

Code kind qr writes a scannable code. raw-bytes is the same payload as a file, for tests that do not want a camera.

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.

    QR fps

    What this builds

    A tiny first-person game in a corridor or two, packed into a payload that a QR code can carry. The world, the art and the palette are original. No copyrighted IWAD or commercial asset is used, in the build or in the checks. A test can decode the payload (from the QR image or from the raw bytes), boot the game, walk a scripted path, and assert a position and an item pickup. A golden frame is taken in the corridor.

    Read spekkr.inputs.json first. title is on the boot screen. scale sizes the written QR image. code chooses a QR or a raw payload file. minimap and dither change the picture, not the world.

    Out of scope

    • Any copyrighted commercial game data or name in the UI or the files.
    • A camera in the checks; decoding uses a library on the written image, or the raw bytes.
    • Network, multiplayer, or a level editor in this version.

    Requirements

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

    R1. The payload
    • The world, the textures, and a tiny engine are packed into a documented payload of at most 2,953 bytes (QR version 40, binary, if code is qr; the raw file must be the same bytes).
    • A packer writes the payload and, if code is qr, a PNG of the code at scale.
    • A decoder reads the PNG or the raw file and recovers the exact bytes.

    Accept when: the packed bytes are at most 2,953, the QR PNG decodes to those bytes, and the raw file matches them.

    R2. Boot and walk
    • Boot shows title for 2 seconds (tests may skip the wait) and then the first-person view at the spawn in design.md.
    • fixtures/qr-walk.json is a list of steps (turn, forward) that ends at a documented position and heading, and picks up item key-0.
    • The walk is deterministic. Collision with walls is a slide along the wall.

    Accept when: after the walk, position and heading match the file within 0.05 units and 0.5 degrees, and key-0 is in the inventory.

    R3. Frames and rights
    • Frames: the QR image, the boot title, the corridor at spawn, and the view at the pickup step.
    • A licence file lists every asset and states they are original or permissively licensed. A test fails if a known copyrighted IWAD filename or marker is present in the repo.

    Accept when: the four frames match the goldens, and the IWAD scan is clean.

    R4. Files
    • One command packs, decodes, walks, scans, and writes the frames. No network. No camera.

    Accept when: the command passes for both code kinds.

    R5. 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

    The payload decodes (from a written QR or from raw bytes) and boots. A scripted walkthrough asserts a final position, heading, and an item pickup. A golden corridor frame is checked. A scan fails the build if a copyrighted IWAD is present. No camera and no network in the checks.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to pack the code, how to play, and how to run the checks.
    # QR fps
    
    ## What this builds
    
    A tiny first-person game in a corridor or two, packed into a payload that
    a QR code can carry. The world, the art and the palette are original. No
    copyrighted IWAD or commercial asset is used, in the build or in the
    checks. A test can decode the payload (from the QR image or from the raw
    bytes), boot the game, walk a scripted path, and assert a position and an
    item pickup. A golden frame is taken in the corridor.
    
    Read `spekkr.inputs.json` first. `title` is on the boot screen. `scale`
    sizes the written QR image. `code` chooses a QR or a raw payload file.
    `minimap` and `dither` change the picture, not the world.
    
    ## Out of scope
    
    - Any copyrighted commercial game data or name in the UI or the files.
    - A camera in the checks; decoding uses a library on the written image, or
      the raw bytes.
    - Network, multiplayer, or a level editor in this version.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. The payload
    
    - The world, the textures, and a tiny engine are packed into a documented
      payload of at most 2,953 bytes (QR version 40, binary, if `code` is
      `qr`; the raw file must be the same bytes).
    - A packer writes the payload and, if `code` is `qr`, a PNG of the code at
      `scale`.
    - A decoder reads the PNG or the raw file and recovers the exact bytes.
    
    Accept when: the packed bytes are at most 2,953, the QR PNG decodes to
    those bytes, and the raw file matches them.
    
    ### R2. Boot and walk
    
    - Boot shows `title` for 2 seconds (tests may skip the wait) and then the
      first-person view at the spawn in `design.md`.
    - `fixtures/qr-walk.json` is a list of steps (turn, forward) that ends at
      a documented position and heading, and picks up item `key-0`.
    - The walk is deterministic. Collision with walls is a slide along the
      wall.
    
    Accept when: after the walk, position and heading match the file within
    0.05 units and 0.5 degrees, and `key-0` is in the inventory.
    
    ### R3. Frames and rights
    
    - Frames: the QR image, the boot title, the corridor at spawn, and the
      view at the pickup step.
    - A licence file lists every asset and states they are original or
      permissively licensed. A test fails if a known copyrighted IWAD filename
      or marker is present in the repo.
    
    Accept when: the four frames match the goldens, and the IWAD scan is
    clean.
    
    ### R4. Files
    
    - One command packs, decodes, walks, scans, and writes the frames. No
      network. No camera.
    
    Accept when: the command passes for both `code` kinds.
    
    ### R5. 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
    
    The payload decodes (from a written QR or from raw bytes) and boots. A
    scripted walkthrough asserts a final position, heading, and an item
    pickup. A golden corridor frame is checked. A scan fails the build if a
    copyrighted IWAD is present. No camera and no network in the checks.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to pack the code, how to play, and how to run the
      checks.
    

    Open spec.md as plain text

  • design.md The payload cap, the map, and the scripted walk and pickup.

    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.

    World

    A 16 by 16 grid, cell size 1. Walls are 1, open is 0, the map is fixtures/qr-map.txt. Spawn is (3.5, 3.5), heading 0 (east). Item key-0 is at (10.5, 3.5).

    Walk

    fixtures/qr-walk.json is the authority for steps and for the end pose. The engine steps at 1/30 s. Forward speed 3 units/s, turn 120 degrees/s.

    Payload

    The packer layout (header, map, textures, code) is docs in the built project. Tests only require: size cap, round-trip, and that the walk works after a decode.

    Screenshot tolerance

    8 levels, 98% of pixels. The QR image is compared after a decode-and-re-encode may differ; the check is that it decodes, plus a visual tolerance of 16 levels.

    Inputs

    KeyLabelDefaultNotes
    titleTitle on the boot screenA small corridorShown for two seconds at boot.
    scaleQR module scale, px6From 4 to 10, for the written code image.
    minimapShow a minimapoffA tiny top-down map in the corner after boot.
    ditherDither the frameonThe world is drawn with a small dither, so it packs and still reads.
    codeCode kindqrqr writes a scannable code. raw-bytes is the same payload as a file, for tests that do not want a 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.

    FixtureRole
    design.mdA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/qr-map.txtA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/qr-walk.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/corridor.pngThe small corridor, walls packed with scannable modules.

    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. The payload decodes (from a written QR or from raw bytes) and boots. A scripted walkthrough asserts a final position, heading, and an item pickup. A golden corridor frame is checked. A scan fails the build if a copyrighted IWAD is present. No camera and no network in the checks.
    # 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.
    
    ## World
    
    A 16 by 16 grid, cell size 1. Walls are 1, open is 0, the map is
    `fixtures/qr-map.txt`. Spawn is (3.5, 3.5), heading 0 (east). Item `key-0`
    is at (10.5, 3.5).
    
    ## Walk
    
    `fixtures/qr-walk.json` is the authority for steps and for the end pose.
    The engine steps at 1/30 s. Forward speed 3 units/s, turn 120 degrees/s.
    
    ## Payload
    
    The packer layout (header, map, textures, code) is `docs` in the built
    project. Tests only require: size cap, round-trip, and that the walk works
    after a decode.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. The QR image is compared after a
    decode-and-re-encode may differ; the check is that it decodes, plus a
    visual tolerance of 16 levels.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title on the boot screen | A small corridor | Shown for two seconds at boot. |
    | `scale` | QR module scale, px | 6 | From 4 to 10, for the written code image. |
    | `minimap` | Show a minimap | off | A tiny top-down map in the corner after boot. |
    | `dither` | Dither the frame | on | The world is drawn with a small dither, so it packs and still reads. |
    | `code` | Code kind | qr | qr writes a scannable code. raw-bytes is the same payload as a file, for tests that do not want a 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 |
    | --- | --- |
    | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/qr-map.txt` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/qr-walk.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/corridor.png` | The small corridor, walls packed with scannable modules. |
    
    
    ## 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. The payload decodes (from a written QR or from raw bytes) and boots. A
    scripted walkthrough asserts a final position, heading, and an item
    pickup. A golden corridor frame is checked. A scan fails the build if a
    copyrighted IWAD is present. No camera and no network in the checks.
    

    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. The payload (R1). Build what R1. The payload asks for, to the numbers in design.md. In particular: The world, the textures, and a tiny engine are packed into a documented payload of at most 2,953 bytes (QR version 40, binary, if code is qr; the raw file must be the same bytes). Check: the R1. The payload acceptance checks pass.
    3. Boot and walk (R2). Build what R2. Boot and walk asks for, to the numbers in design.md. In particular: Boot shows title for 2 seconds (tests may skip the wait) and then the first-person view at the spawn in design.md. Check: the R2. Boot and walk acceptance checks pass.
    4. Frames and rights (R3). Build what R3. Frames and rights asks for, to the numbers in design.md. In particular: Frames: the QR image, the boot title, the corridor at spawn, and the view at the pickup step. Check: the R3. Frames and rights acceptance checks pass.
    5. Files (R4). Build what R4. Files asks for, to the numbers in design.md. In particular: One command packs, decodes, walks, scans, and writes the frames. No network. No camera. Check: the R4. Files acceptance checks pass.
    6. Inputs (R5). Build what R5. 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 R5. Inputs acceptance checks pass.
    7. 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.
    8. 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. **The payload (R1).** Build what `R1. The payload` asks for, to the
    numbers in `design.md`. In particular: The world, the textures, and a tiny
    engine are packed into a documented payload of at most 2,953 bytes (QR
    version 40, binary, if `code` is `qr`; the raw file must be the same
    bytes).
       Check: the `R1. The payload` acceptance checks pass.
    
    3. **Boot and walk (R2).** Build what `R2. Boot and walk` asks for, to the
    numbers in `design.md`. In particular: Boot shows `title` for 2 seconds
    (tests may skip the wait) and then the first-person view at the spawn in
    `design.md`.
       Check: the `R2. Boot and walk` acceptance checks pass.
    
    4. **Frames and rights (R3).** Build what `R3. Frames and rights` asks
    for, to the numbers in `design.md`. In particular: Frames: the QR image,
    the boot title, the corridor at spawn, and the view at the pickup step.
       Check: the `R3. Frames and rights` acceptance checks pass.
    
    5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in
    `design.md`. In particular: One command packs, decodes, walks, scans, and
    writes the frames. No network. No camera.
       Check: the `R4. Files` acceptance checks pass.
    
    6. **Inputs (R5).** Build what `R5. 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 `R5. Inputs` acceptance checks pass.
    
    7. **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.
    
    8. **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 writes and reads a QR code 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.