Isometric city

A browsable isometric pixel city: a fixture coordinate shows a documented tile, with pan and zoom goldens.

This is a creative tool 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/isometric-city
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

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

Isometric city: heroIsometric city: closeIsometric city: loop

What can I customize?

City A shipped tile map. small is a 16 by 16 fixture.

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.

    Isometric city

    What this builds

    A large isometric map you can pan and zoom, made of pixel-art tiles and a few named buildings. The city is original, not a tracing of a real one. A fixture coordinate must show a documented tile or building. Pan and zoom have golden frames. The craft is in the tiles and the camera, not in a live dataset.

    Read spekkr.inputs.json first. title sits in the margin. tile is the diamond size. city chooses the map. labels and grid change the chrome.

    Out of scope

    • A live map of a real city, or a copyrighted skyline.
    • Network or a streaming tile server in the checks.
    • A 3D mesh of every building in this version.

    Requirements

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

    R1. Coordinates and tiles
    • The map is a 2D grid of tile ids, drawn in a standard diamond isometric projection, documented in design.md.
    • The fixture fixtures/riverport-at.json lists coordinates that must show the stated tile id or building id at the centre of the view.
    • A coordinate outside the map is clamped, not wrapped, unless a later option says so (this version does not wrap).

    Accept when: every listed coordinate shows the stated id, and an out-of-range coordinate is clamped to the last tile.

    R2. Pan, zoom, frames
    • Zoom levels are 0.5, 1, and 2, times the tile size. Pan is in tile coordinates.
    • Goldens: an overview at 0.5, a landmark at 1, a zoomed 2, and a panned view at the second fixture coordinate.
    • One command looks up the fixtures, takes the frames, and compares them. No network.

    Accept when: the four frames match the goldens, and a pixel at the view centre of the landmark frame is in the building's mask file.

    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

    A fixture coordinate shows the documented tile or building, checked by id and by a centre-pixel mask. Pan and zoom have golden screenshots at documented levels. No live city 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 pan, how to add a tile, and how to run the checks.
    # Isometric city
    
    ## What this builds
    
    A large isometric map you can pan and zoom, made of pixel-art tiles and a
    few named buildings. The city is original, not a tracing of a real one. A
    fixture coordinate must show a documented tile or building. Pan and zoom
    have golden frames. The craft is in the tiles and the camera, not in a
    live dataset.
    
    Read `spekkr.inputs.json` first. `title` sits in the margin. `tile` is the
    diamond size. `city` chooses the map. `labels` and `grid` change the
    chrome.
    
    ## Out of scope
    
    - A live map of a real city, or a copyrighted skyline.
    - Network or a streaming tile server in the checks.
    - A 3D mesh of every building in this version.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Coordinates and tiles
    
    - The map is a 2D grid of tile ids, drawn in a standard diamond isometric
      projection, documented in `design.md`.
    - The fixture `fixtures/riverport-at.json` lists coordinates that must
      show the stated tile id or building id at the centre of the view.
    - A coordinate outside the map is clamped, not wrapped, unless a later
      option says so (this version does not wrap).
    
    Accept when: every listed coordinate shows the stated id, and an
    out-of-range coordinate is clamped to the last tile.
    
    ### R2. Pan, zoom, frames
    
    - Zoom levels are 0.5, 1, and 2, times the `tile` size. Pan is in tile
      coordinates.
    - Goldens: an overview at 0.5, a landmark at 1, a zoomed 2, and a panned
      view at the second fixture coordinate.
    - One command looks up the fixtures, takes the frames, and compares them.
      No network.
    
    Accept when: the four frames match the goldens, and a pixel at the view
    centre of the landmark frame is in the building's mask file.
    
    ### 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
    
    A fixture coordinate shows the documented tile or building, checked by id
    and by a centre-pixel mask. Pan and zoom have golden screenshots at
    documented levels. No live city 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 pan, how to add a tile, and how to run the checks.
    

    Open spec.md as plain text

  • design.md The isometric projection, fixture coordinates, and pan/zoom goldens.

    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.

    Projection

    Tile (i, j) has its top at x = (i - j) * tile/2, y = (i + j) * tile/4, plus a camera offset. The file fixtures/riverport-at.json is the authority for which building sits at which (i, j).

    Screenshot tolerance

    8 levels, 98% of pixels. The centre-tile id check is exact.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA city of tilesShown in a margin.
    tileTile size, px32The width of one isometric diamond, 16, 32 or 64.
    labelsLabel landmarksonA name on documented buildings.
    gridShow a faint gridoffTile outlines, useful in tests.
    cityCityriverportA shipped tile map. small is a 16 by 16 fixture.

    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/riverport-at.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/dusk.pngDusk over the harbour, an isometric pixel city, tile 32.

    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. A fixture coordinate shows the documented tile or building, checked by id and by a centre-pixel mask. Pan and zoom have golden screenshots at documented levels. No live city 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.
    
    ## Projection
    
    Tile (i, j) has its top at `x = (i - j) * tile/2`, `y = (i + j) * tile/4`,
    plus a camera offset. The file `fixtures/riverport-at.json` is the
    authority for which building sits at which (i, j).
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. The centre-tile id check is exact.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A city of tiles | Shown in a margin. |
    | `tile` | Tile size, px | 32 | The width of one isometric diamond, 16, 32 or 64. |
    | `labels` | Label landmarks | on | A name on documented buildings. |
    | `grid` | Show a faint grid | off | Tile outlines, useful in tests. |
    | `city` | City | riverport | A shipped tile map. small is a 16 by 16 fixture. |
    
    ## 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/riverport-at.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/dusk.png` | Dusk over the harbour, an isometric pixel city, tile 32. |
    
    
    ## 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. A fixture coordinate shows the documented tile or building, checked by
    id and by a centre-pixel mask. Pan and zoom have golden screenshots at
    documented levels. No live city 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. Coordinates and tiles (R1). Build what R1. Coordinates and tiles asks for, to the numbers in design.md. In particular: The map is a 2D grid of tile ids, drawn in a standard diamond isometric projection, documented in design.md. Check: the R1. Coordinates and tiles acceptance checks pass.
    3. Pan, zoom, frames (R2). Build what R2. Pan, zoom, frames asks for, to the numbers in design.md. In particular: Zoom levels are 0.5, 1, and 2, times the tile size. Pan is in tile coordinates. Check: the R2. Pan, zoom, 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.
    # 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. **Coordinates and tiles (R1).** Build what `R1. Coordinates and tiles`
    asks for, to the numbers in `design.md`. In particular: The map is a 2D
    grid of tile ids, drawn in a standard diamond isometric projection,
    documented in `design.md`.
       Check: the `R1. Coordinates and tiles` acceptance checks pass.
    
    3. **Pan, zoom, frames (R2).** Build what `R2. Pan, zoom, frames` asks
    for, to the numbers in `design.md`. In particular: Zoom levels are 0.5, 1,
    and 2, times the `tile` size. Pan is in tile coordinates.
       Check: the `R2. Pan, zoom, 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.
    

    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/GeistMono.ttf Geist Mono 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 2026Tighten the city crop, light more windows, 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.