Apartment planner

Walk and furnish a small flat in the browser: fixture furniture and room sizes, collision tests, and a golden view, with a shareable layout.

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/apartment-planner
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

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

Apartment planner: heroApartment planner: loop

What can I customize?

Flat A shipped room plan, in metres.

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.

    Apartment planner

    What this builds

    A small apartment you can furnish and walk through in the browser. Rooms have documented sizes. Furniture comes from a shipped set. Layouts serialise to a shareable state URL. Tests place a fixture layout, check room dimensions, and assert collisions and bounds. A golden view is taken. The furniture and the flats are original.

    Read spekkr.inputs.json first. title is on the plan. flat chooses the rooms. walk and collisions change the view and the rules. share_prefix is used for a URL.

    Out of scope

    • A real-estate listing, a live catalogue, or a paid furniture store.
    • Network or a public gallery in the checks.
    • Structural or electrical plans.

    Requirements

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

    R1. Rooms and furniture
    • Each flat's rooms and sizes are in fixtures/flats.json, in metres, and the bounding box of each room matches within 0.01 m.
    • The fixture layout fixtures/studio-a.json places listed pieces at documented poses. Loading it restores those poses within 0.01 m and 0.5 degrees.
    • The share URL of that layout, under share_prefix, round-trips to the same state.

    Accept when: sizes and poses match, and the URL round-trips.

    R2. Collisions and walk
    • If collisions is on, a move that would overlap a wall or another piece is refused. The cases in fixtures/apt-collisions.json hold.
    • A walk, if on, starts at the documented door and a scripted path ends at the pose in the file, sliding along a wall rather than passing through it.
    • If collisions is off, the refuse cases become allowed; a test covers that too.

    Accept when: every collision case matches the option, and the walk ends at the documented pose.

    R3. Frames and files
    • Goldens: the empty plan, the fixture furnished, a first-person view, and a collision-refused overlay.
    • One command runs sizes, poses, URL, collisions, and the walk, and writes the frames. No network.

    Accept when: the command passes for both flats, 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

    Fixture furniture poses and room dimensions match shipped files. Collision and bounds cases are tested with the option on and off. A scripted walk does not pass through walls. A layout round-trips through a share URL. A golden view is checked. No live catalogue 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 furnish, how to share a layout, and how to run the checks.
    # Apartment planner
    
    ## What this builds
    
    A small apartment you can furnish and walk through in the browser. Rooms
    have documented sizes. Furniture comes from a shipped set. Layouts
    serialise to a shareable state URL. Tests place a fixture layout, check
    room dimensions, and assert collisions and bounds. A golden view is taken.
    The furniture and the flats are original.
    
    Read `spekkr.inputs.json` first. `title` is on the plan. `flat` chooses
    the rooms. `walk` and `collisions` change the view and the rules.
    `share_prefix` is used for a URL.
    
    ## Out of scope
    
    - A real-estate listing, a live catalogue, or a paid furniture store.
    - Network or a public gallery in the checks.
    - Structural or electrical plans.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Rooms and furniture
    
    - Each flat's rooms and sizes are in `fixtures/flats.json`, in metres, and
      the bounding box of each room matches within 0.01 m.
    - The fixture layout `fixtures/studio-a.json` places listed pieces at
      documented poses. Loading it restores those poses within 0.01 m and 0.5
      degrees.
    - The share URL of that layout, under `share_prefix`, round-trips to the
      same state.
    
    Accept when: sizes and poses match, and the URL round-trips.
    
    ### R2. Collisions and walk
    
    - If `collisions` is on, a move that would overlap a wall or another piece
      is refused. The cases in `fixtures/apt-collisions.json` hold.
    - A walk, if on, starts at the documented door and a scripted path ends at
      the pose in the file, sliding along a wall rather than passing through
      it.
    - If `collisions` is off, the refuse cases become allowed; a test covers
      that too.
    
    Accept when: every collision case matches the option, and the walk ends at
    the documented pose.
    
    ### R3. Frames and files
    
    - Goldens: the empty plan, the fixture furnished, a first-person view, and
      a collision-refused overlay.
    - One command runs sizes, poses, URL, collisions, and the walk, and writes
      the frames. No network.
    
    Accept when: the command passes for both flats, 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
    
    Fixture furniture poses and room dimensions match shipped files. Collision
    and bounds cases are tested with the option on and off. A scripted walk
    does not pass through walls. A layout round-trips through a share URL. A
    golden view is checked. No live catalogue 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 furnish, how to share a layout, and how to run the
      checks.
    

    Open spec.md as plain text

  • design.md Room sizes, the fixture layout, collisions, and the share URL.

    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.

    Studio

    A single room 6.2 by 4.1 m, walls 0.15 m, door 0.9 m on the south wall. The one-bed flat is in the same file. Furniture bounding boxes are in fixtures/furniture.json.

    Screenshot tolerance

    8 levels, 98% of pixels.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA small flatShown on the plan.
    share_prefixShare URL prefixhttps://example.invalid/a/Used when minting a layout URL.
    walkFirst-person walkonIf off, only a top-down plan is used.
    collisionsBlock intersectionsonFurniture cannot overlap walls or each other.
    flatFlatstudioA shipped room plan, in metres.

    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
    fixtures/apt-collisions.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/flats.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/furniture.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/studio-a.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/plan.pngA small furnished flat: living, kitchen, bedroom, bath, a plant still in hand.

    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 furniture poses and room dimensions match shipped files. Collision and bounds cases are tested with the option on and off. A scripted walk does not pass through walls. A layout round-trips through a share URL. A golden view is checked. No live catalogue 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.
    
    ## Studio
    
    A single room 6.2 by 4.1 m, walls 0.15 m, door 0.9 m on the south wall.
    The one-bed flat is in the same file. Furniture bounding boxes are in
    `fixtures/furniture.json`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A small flat | Shown on the plan. |
    | `share_prefix` | Share URL prefix | https://example.invalid/a/ | Used when minting a layout URL. |
    | `walk` | First-person walk | on | If off, only a top-down plan is used. |
    | `collisions` | Block intersections | on | Furniture cannot overlap walls or each other. |
    | `flat` | Flat | studio | A shipped room plan, in metres. |
    
    ## 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/apt-collisions.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/flats.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/furniture.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/studio-a.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/plan.png` | A small furnished flat: living, kitchen, bedroom, bath, a plant still in hand. |
    
    
    ## 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 furniture poses and room dimensions match shipped files.
    Collision and bounds cases are tested with the option on and off. A
    scripted walk does not pass through walls. A layout round-trips through a
    share URL. A golden view is checked. No live catalogue 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. Rooms and furniture (R1). Build what R1. Rooms and furniture asks for, to the numbers in design.md. In particular: Each flat's rooms and sizes are in fixtures/flats.json, in metres, and the bounding box of each room matches within 0.01 m. Check: the R1. Rooms and furniture acceptance checks pass.
    3. Collisions and walk (R2). Build what R2. Collisions and walk asks for, to the numbers in design.md. In particular: If collisions is on, a move that would overlap a wall or another piece is refused. The cases in fixtures/apt-collisions.json hold. Check: the R2. Collisions and walk acceptance checks pass.
    4. Frames and files (R3). Build what R3. Frames and files asks for, to the numbers in design.md. In particular: Goldens: the empty plan, the fixture furnished, a first-person view, and a collision-refused overlay. 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.
    # 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. **Rooms and furniture (R1).** Build what `R1. Rooms and furniture` asks
    for, to the numbers in `design.md`. In particular: Each flat's rooms and
    sizes are in `fixtures/flats.json`, in metres, and the bounding box of
    each room matches within 0.01 m.
       Check: the `R1. Rooms and furniture` acceptance checks pass.
    
    3. **Collisions and walk (R2).** Build what `R2. Collisions and walk` asks
    for, to the numbers in `design.md`. In particular: If `collisions` is on,
    a move that would overlap a wall or another piece is refused. The cases in
    `fixtures/apt-collisions.json` hold.
       Check: the `R2. Collisions and walk` acceptance checks pass.
    
    4. **Frames and files (R3).** Build what `R3. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: the empty plan, the
    fixture furnished, a first-person view, and a collision-refused overlay.
       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.
    

    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, WebGL

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 2026Add floorboards, window depth, furniture shadows, and 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.