Retro desktop

A miniature desktop in the browser, with tests for windows, icons and two built-in apps, and a golden desktop shot.

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

Build this spec

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

Retro desktop: heroRetro desktop: hoursRetro desktop: loop

What can I customize?

Skin An original look. Not a copy of a commercial desktop.

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.

    Retro desktop

    What this builds

    A desktop in a browser tab: a wallpaper, icons, a menu, overlapping windows, and a couple of built-in apps (a notes pad and a tiny paint). It can be used as a playground or a portfolio shell. The look is nostalgic but original — it is not a copy of a commercial operating system, and it does not use that system's marks. Tests cover windowing, icons, and the two apps, plus a golden desktop shot.

    Read spekkr.inputs.json first. title and user_name appear in the chrome. skin chooses the look. login and clock change the first screen and the menu bar. The clock is injectable.

    Out of scope

    • A real operating system, or a clone of a trademarked desktop.
    • Network, accounts, or a guest file system beyond a session.
    • Running third-party binaries.

    Requirements

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

    R1. Windowing and icons
    • A double-activate (or a documented single click) on an icon opens that app in a window. Two windows can be open at once; the last clicked is on top.
    • A window can be moved, resized within min sizes in design.md, closed, and (if a control exists) minimised to a bar.
    • The icon positions of the default desktop are in fixtures/desktop-icons.json.

    Accept when: opening notes then paint produces two windows, paint is on top, and a move/resize/close script matches the fixture end state.

    R2. The two apps
    • Notes: typing a fixture string and then reading the notes file (or the in-memory buffer) returns that string. A save and a reload, in-session, keeps it.
    • Paint: a scripted stroke leaves the pixel at a listed coordinate within 8 levels of the chosen colour. A clear returns the paper colour.
    • Neither app requires a network.

    Accept when: the notes string round-trips, and the paint pixel and clear checks pass.

    R3. Frames and files
    • Goldens: the empty desktop, two windows, notes with the fixture string, and paint after the stroke. Time, if shown, is the injected 14:00.
    • One command runs windowing, apps, and writes the frames. No network.

    Accept when: the command passes for every skin, and the frames match (skins have sibling goldens or a documented chrome-only mask).

    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

    Windowing, icons, and two built-in apps (notes and paint) have behavior tests, including a notes round-trip and a paint pixel check. A golden desktop shot is taken with an injected clock. The skin is original and does not use a commercial OS mark. 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 open an app, how to add an icon, and how to run the checks.
    # Retro desktop
    
    ## What this builds
    
    A desktop in a browser tab: a wallpaper, icons, a menu, overlapping
    windows, and a couple of built-in apps (a notes pad and a tiny paint). It
    can be used as a playground or a portfolio shell. The look is nostalgic
    but original — it is not a copy of a commercial operating system, and it
    does not use that system's marks. Tests cover windowing, icons, and the
    two apps, plus a golden desktop shot.
    
    Read `spekkr.inputs.json` first. `title` and `user_name` appear in the
    chrome. `skin` chooses the look. `login` and `clock` change the first
    screen and the menu bar. The clock is injectable.
    
    ## Out of scope
    
    - A real operating system, or a clone of a trademarked desktop.
    - Network, accounts, or a guest file system beyond a session.
    - Running third-party binaries.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Windowing and icons
    
    - A double-activate (or a documented single click) on an icon opens that
      app in a window. Two windows can be open at once; the last clicked is on
      top.
    - A window can be moved, resized within min sizes in `design.md`, closed,
      and (if a control exists) minimised to a bar.
    - The icon positions of the default desktop are in
      `fixtures/desktop-icons.json`.
    
    Accept when: opening notes then paint produces two windows, paint is on
    top, and a move/resize/close script matches the fixture end state.
    
    ### R2. The two apps
    
    - Notes: typing a fixture string and then reading the notes file (or the
      in-memory buffer) returns that string. A save and a reload, in-session,
      keeps it.
    - Paint: a scripted stroke leaves the pixel at a listed coordinate within
      8 levels of the chosen colour. A clear returns the paper colour.
    - Neither app requires a network.
    
    Accept when: the notes string round-trips, and the paint pixel and clear
    checks pass.
    
    ### R3. Frames and files
    
    - Goldens: the empty desktop, two windows, notes with the fixture string,
      and paint after the stroke. Time, if shown, is the injected 14:00.
    - One command runs windowing, apps, and writes the frames. No network.
    
    Accept when: the command passes for every skin, and the frames match
    (skins have sibling goldens or a documented chrome-only mask).
    
    ### 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
    
    Windowing, icons, and two built-in apps (notes and paint) have behavior
    tests, including a notes round-trip and a paint pixel check. A golden
    desktop shot is taken with an injected clock. The skin is original and
    does not use a commercial OS mark. 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 open an app, how to add an icon, and how to run the
      checks.
    

    Open spec.md as plain text

  • design.md Icon layout, windowing, and the two built-in apps.

    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.

    Window min size

    Notes 240 by 160, paint 320 by 240, in CSS pixels. Desktop is 1600 by 1000 for goldens.

    Screenshot tolerance

    8 levels, 98% of pixels. Injected clock is 14:00 on 2026-01-15.

    Inputs

    KeyLabelDefaultNotes
    titleDesktop titleMillstead workstationShown on the start screen or the menu bar.
    user_nameUser nameadaShown on the login or the menu.
    loginShow a login firstoffA decorative login; the password is empty or a fixture, not a real account.
    clockShow a clockonTests inject the time.
    skinSkinmeadowAn original look. Not a copy of a commercial desktop.

    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/desktop-icons.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/desktop.pngMillstead workstation, user ada, Readme and Sketch both 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. Windowing, icons, and two built-in apps (notes and paint) have behavior tests, including a notes round-trip and a paint pixel check. A golden desktop shot is taken with an injected clock. The skin is original and does not use a commercial OS mark. 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.
    
    ## Window min size
    
    Notes 240 by 160, paint 320 by 240, in CSS pixels. Desktop is 1600 by 1000
    for goldens.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. Injected clock is 14:00 on 2026-01-15.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Desktop title | Millstead workstation | Shown on the start screen or the menu bar. |
    | `user_name` | User name | ada | Shown on the login or the menu. |
    | `login` | Show a login first | off | A decorative login; the password is empty or a fixture, not a real account. |
    | `clock` | Show a clock | on | Tests inject the time. |
    | `skin` | Skin | meadow | An original look. Not a copy of a commercial desktop. |
    
    ## 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/desktop-icons.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/desktop.png` | Millstead workstation, user ada, Readme and Sketch both 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. Windowing, icons, and two built-in apps (notes and paint) have behavior
    tests, including a notes round-trip and a paint pixel check. A golden
    desktop shot is taken with an injected clock. The skin is original and
    does not use a commercial OS mark. 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. Windowing and icons (R1). Build what R1. Windowing and icons asks for, to the numbers in design.md. In particular: A double-activate (or a documented single click) on an icon opens that app in a window. Two windows can be open at once; the last clicked is on top. Check: the R1. Windowing and icons acceptance checks pass.
    3. The two apps (R2). Build what R2. The two apps asks for, to the numbers in design.md. In particular: Notes: typing a fixture string and then reading the notes file (or the in-memory buffer) returns that string. A save and a reload, in-session, keeps it. Check: the R2. The two apps 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 desktop, two windows, notes with the fixture string, and paint after the stroke. Time, if shown, is the injected 14:00. 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. **Windowing and icons (R1).** Build what `R1. Windowing and icons` asks
    for, to the numbers in `design.md`. In particular: A double-activate (or a
    documented single click) on an icon opens that app in a window. Two
    windows can be open at once; the last clicked is on top.
       Check: the `R1. Windowing and icons` acceptance checks pass.
    
    3. **The two apps (R2).** Build what `R2. The two apps` asks for, to the
    numbers in `design.md`. In particular: Notes: typing a fixture string and
    then reading the notes file (or the in-memory buffer) returns that string.
    A save and a reload, in-session, keeps it.
       Check: the `R2. The two apps` 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 desktop,
    two windows, notes with the fixture string, and paint after the stroke.
    Time, if shown, is the injected 14:00.
       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/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.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.