Critter slide

A sliding puzzle where two kinds of animal move by different rules, with known solvable and unsolvable positions.

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

Build this spec

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

Critter slide: heroCritter slide: solvedCritter slide: loop

What can I customize?

Level pack intro is five levels. full is fifteen.

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.

    Critter slide

    What this builds

    A grid puzzle. Hoppers move any number of empty squares like a rook, but only horizontally. Hoppers cannot pass a blocker. Hoppers want to reach a burrow of their own colour. Blockers move one square orthogonally, cannot enter a burrow, and are used to open or close paths. The rules are original. A level is a starting grid and a goal test: every hopper on a burrow of its colour.

    Read spekkr.inputs.json first. title labels the board. size is the default size for a fresh editor grid; shipped levels carry their own size. pack chooses the level set. hints and undo add controls.

    Out of scope

    • A public level workshop in the first version.
    • Animated 3D animals or sound beyond a single move pip.
    • Network, accounts or a leaderboard.

    Requirements

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

    R1. Movement
    • Hoppers (H and h for two colours) slide any number of clear squares along a row, never a column, and never through or onto a blocker (B) or another hopper.
    • Blockers move one clear orthogonal square, never onto a burrow (O or o) or another piece.
    • A move that would leave the board is illegal. Empty squares are ..

    Accept when: the movement fixtures in design.md each produce the stated legal set, and no illegal move is accepted.

    R2. A known solvable level
    • Level I1 in the intro pack is the 5 by 5 grid in design.md.
    • The documented seven-move solution reaches a solved state, and a solver check reports it solvable in at most 7 moves.

    Accept when: applying the seven moves leaves every hopper on its burrow, and a breadth-first search finds a solution of length 7 or less.

    R3. A known unsolvable position
    • Position U1 in design.md is not solvable: a hopper is boxed in with no path to its burrow, even with blocker help.
    • A search that expands every position up to 30 moves reports no solution, and the UI's give-up check agrees.

    Accept when: a search of U1 reports unsolvable, and a hopper move that would seem to help is illegal as in the table.

    R4. Levels and chrome
    • Each pack is a file of levels. A level has an id, a grid, and the documented solution length for solvable ones, or unsolvable.
    • If hints is on, a control highlights every piece that has at least one legal move.
    • If undo is on, each move can be stepped back in order, back to the start.

    Accept when: I1 loads from the file, hints highlight the two pieces named in design.md at the start, and undo after two moves restores the start.

    R5. Screenshots and files
    • Frames: start of I1, mid-solve after three documented moves, solved after seven, blocked of U1.
    • One command runs movement tests, the solvability checks, and writes the screenshots.

    Accept when: the command passes for both packs, and the frames match within the tolerance in design.md.

    Verification

    Unit tests cover hopper and blocker movement, including illegal moves off the board and through blockers. The documented I1 solution solves the level; a search agrees it is solvable in at most 7 moves. Position U1 is reported unsolvable. Golden frames are taken for a short solve and for the blocked position. No physical pieces 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 play, how to run the checks, and how to add a level.
    # Critter slide
    
    ## What this builds
    
    A grid puzzle. Hoppers move any number of empty squares like a rook, but
    only horizontally. Hoppers cannot pass a blocker. Hoppers want to reach a
    burrow of their own colour. Blockers move one square orthogonally, cannot
    enter a burrow, and are used to open or close paths. The rules are
    original. A level is a starting grid and a goal test: every hopper on a
    burrow of its colour.
    
    Read `spekkr.inputs.json` first. `title` labels the board. `size` is the
    default size for a fresh editor grid; shipped levels carry their own size.
    `pack` chooses the level set. `hints` and `undo` add controls.
    
    ## Out of scope
    
    - A public level workshop in the first version.
    - Animated 3D animals or sound beyond a single move pip.
    - Network, accounts or a leaderboard.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Movement
    
    - Hoppers (`H` and `h` for two colours) slide any number of clear squares
      along a row, never a column, and never through or onto a blocker (`B`)
      or another hopper.
    - Blockers move one clear orthogonal square, never onto a burrow (`O` or
      `o`) or another piece.
    - A move that would leave the board is illegal. Empty squares are `.`.
    
    Accept when: the movement fixtures in `design.md` each produce the stated
    legal set, and no illegal move is accepted.
    
    ### R2. A known solvable level
    
    - Level I1 in the intro pack is the 5 by 5 grid in `design.md`.
    - The documented seven-move solution reaches a solved state, and a solver
      check reports it solvable in at most 7 moves.
    
    Accept when: applying the seven moves leaves every hopper on its burrow,
    and a breadth-first search finds a solution of length 7 or less.
    
    ### R3. A known unsolvable position
    
    - Position U1 in `design.md` is not solvable: a hopper is boxed in with no
      path to its burrow, even with blocker help.
    - A search that expands every position up to 30 moves reports no solution,
      and the UI's give-up check agrees.
    
    Accept when: a search of U1 reports unsolvable, and a hopper move that
    would seem to help is illegal as in the table.
    
    ### R4. Levels and chrome
    
    - Each pack is a file of levels. A level has an id, a grid, and the
      documented solution length for solvable ones, or `unsolvable`.
    - If `hints` is on, a control highlights every piece that has at least one
      legal move.
    - If `undo` is on, each move can be stepped back in order, back to the
      start.
    
    Accept when: I1 loads from the file, hints highlight the two pieces named
    in `design.md` at the start, and undo after two moves restores the start.
    
    ### R5. Screenshots and files
    
    - Frames: `start` of I1, `mid-solve` after three documented moves,
      `solved` after seven, `blocked` of U1.
    - One command runs movement tests, the solvability checks, and writes the
      screenshots.
    
    Accept when: the command passes for both packs, and the frames match
    within the tolerance in `design.md`.
    
    ## Verification
    
    Unit tests cover hopper and blocker movement, including illegal moves off
    the board and through blockers. The documented I1 solution solves the
    level; a search agrees it is solvable in at most 7 moves. Position U1 is
    reported unsolvable. Golden frames are taken for a short solve and for the
    blocked position. No physical pieces 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 play, how to run the checks, and how to add a
      level.
    

    Open spec.md as plain text

  • design.md Movement rules, the solvable level, the unsolvable position and fixtures.

    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.

    Level I1 (solvable)

    A 5 by 5 grid, rows from the top. H is a hopper of colour A, h of colour B, O a burrow for A, o for B, B a blocker, . empty.

    H . . . O
    . B . . .
    . . . . .
    . . B . .
    o . . . h

    The machine-checked move list is fixtures/i1-moves.json. Tests apply that file, not a re-typed list, to reach a solved board. The file holds seven moves and, applied in order to I1, places every hopper on its burrow.

    The legal movers at the start of I1 are snapshotted in fixtures/i1-legal-start.json. Tests compare the engine's legal set to that file.

    Position U1 (unsolvable)

    H B O . .
    . B . . .
    . . . . .
    . . . . .
    . . . . .

    H cannot pass the blockers to reach O, blockers cannot step onto O, and no other hopper exists. A search to depth 30 finds no solve.

    Packs

    packs/intro.json holds I1–I5 and U1. packs/full.json holds those plus I6–I15, at least three of which are marked unsolvable. Every solvable level ships with a solution file under fixtures/.

    Screenshot tolerance

    Each channel within 8 levels, 98% of pixels, on a 1600 by 1000 frame.

    Inputs

    KeyLabelDefaultNotes
    titleTitleTwo kinds of stepsShown above the board.
    sizeBoard size5Width and height, 4 to 7.
    hintsShow a legal-move hintonA control highlights the pieces that can move now.
    undoAllow undoonA control steps back one move, up to the start of the level.
    packLevel packintrointro is five levels. full is fifteen.

    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/i1-legal-start.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/i1-moves.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    packs/full.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    packs/intro.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/board.pngA 5×5 mid-solve: foxes stride, hares hop, the moss still open.

    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. Unit tests cover hopper and blocker movement, including illegal moves off the board and through blockers. The documented I1 solution solves the level; a search agrees it is solvable in at most 7 moves. Position U1 is reported unsolvable. Golden frames are taken for a short solve and for the blocked position. No physical pieces 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.
    
    ## Level I1 (solvable)
    
    A 5 by 5 grid, rows from the top. `H` is a hopper of colour A, `h` of
    colour B, `O` a burrow for A, `o` for B, `B` a blocker, `.` empty.
    
    ```
    H . . . O
    . B . . .
    . . . . .
    . . B . .
    o . . . h
    ```
    
    The machine-checked move list is `fixtures/i1-moves.json`. Tests apply
    that file, not a re-typed list, to reach a solved board. The file holds
    seven moves and, applied in order to I1, places every hopper on its
    burrow.
    
    The legal movers at the start of I1 are snapshotted in
    `fixtures/i1-legal-start.json`. Tests compare the engine's legal set to
    that file.
    
    ## Position U1 (unsolvable)
    
    ```
    H B O . .
    . B . . .
    . . . . .
    . . . . .
    . . . . .
    ```
    
    `H` cannot pass the blockers to reach `O`, blockers cannot step onto `O`,
    and no other hopper exists. A search to depth 30 finds no solve.
    
    ## Packs
    
    `packs/intro.json` holds I1–I5 and U1. `packs/full.json` holds those plus
    I6–I15, at least three of which are marked unsolvable. Every solvable
    level ships with a solution file under `fixtures/`.
    
    ## Screenshot tolerance
    
    Each channel within 8 levels, 98% of pixels, on a 1600 by 1000 frame.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | Two kinds of steps | Shown above the board. |
    | `size` | Board size | 5 | Width and height, 4 to 7. |
    | `hints` | Show a legal-move hint | on | A control highlights the pieces that can move now. |
    | `undo` | Allow undo | on | A control steps back one move, up to the start of the level. |
    | `pack` | Level pack | intro | intro is five levels. full is fifteen. |
    
    ## 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/i1-legal-start.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/i1-moves.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `packs/full.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `packs/intro.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/board.png` | A 5×5 mid-solve: foxes stride, hares hop, the moss still open. |
    
    
    ## 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. Unit tests cover hopper and blocker movement, including illegal moves
    off the board and through blockers. The documented I1 solution solves the
    level; a search agrees it is solvable in at most 7 moves. Position U1 is
    reported unsolvable. Golden frames are taken for a short solve and for the
    blocked position. No physical pieces 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. Movement (R1). Build what R1. Movement asks for, to the numbers in design.md. In particular: Hoppers (H and h for two colours) slide any number of clear squares along a row, never a column, and never through or onto a blocker (B) or another hopper. Check: the R1. Movement acceptance checks pass.
    3. A known solvable level (R2). Build what R2. A known solvable level asks for, to the numbers in design.md. In particular: Level I1 in the intro pack is the 5 by 5 grid in design.md. Check: the R2. A known solvable level acceptance checks pass.
    4. A known unsolvable position (R3). Build what R3. A known unsolvable position asks for, to the numbers in design.md. In particular: Position U1 in design.md is not solvable: a hopper is boxed in with no path to its burrow, even with blocker help. Check: the R3. A known unsolvable position acceptance checks pass.
    5. Levels and chrome (R4). Build what R4. Levels and chrome asks for, to the numbers in design.md. In particular: Each pack is a file of levels. A level has an id, a grid, and the documented solution length for solvable ones, or unsolvable. Check: the R4. Levels and chrome acceptance checks pass.
    6. Screenshots and files (R5). Build what R5. Screenshots and files asks for, to the numbers in design.md. In particular: Frames: start of I1, mid-solve after three documented moves, solved after seven, blocked of U1. Check: the R5. Screenshots and files 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. **Movement (R1).** Build what `R1. Movement` asks for, to the numbers
    in `design.md`. In particular: Hoppers (`H` and `h` for two colours) slide
    any number of clear squares along a row, never a column, and never through
    or onto a blocker (`B`) or another hopper.
       Check: the `R1. Movement` acceptance checks pass.
    
    3. **A known solvable level (R2).** Build what `R2. A known solvable
    level` asks for, to the numbers in `design.md`. In particular: Level I1 in
    the intro pack is the 5 by 5 grid in `design.md`.
       Check: the `R2. A known solvable level` acceptance checks pass.
    
    4. **A known unsolvable position (R3).** Build what `R3. A known
    unsolvable position` asks for, to the numbers in `design.md`. In
    particular: Position U1 in `design.md` is not solvable: a hopper is boxed
    in with no path to its burrow, even with blocker help.
       Check: the `R3. A known unsolvable position` acceptance checks pass.
    
    5. **Levels and chrome (R4).** Build what `R4. Levels and chrome` asks
    for, to the numbers in `design.md`. In particular: Each pack is a file of
    levels. A level has an id, a grid, and the documented solution length for
    solvable ones, or `unsolvable`.
       Check: the `R4. Levels and chrome` acceptance checks pass.
    
    6. **Screenshots and files (R5).** Build what `R5. Screenshots and files`
    asks for, to the numbers in `design.md`. In particular: Frames: `start` of
    I1, `mid-solve` after three documented moves, `solved` after seven,
    `blocked` of U1.
       Check: the `R5. Screenshots and files` 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/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 2026Redraw the fox and hare as proper pieces, and add 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.