Anti-word

A five-letter daily puzzle with an original word list, where the play is to lose as slowly as possible, with a checked share line.

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

Build this spec

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

Anti-word: heroAnti-word: loop

What can I customize?

Word list standard is the full original list. short is a 200-word fixture list for faster tests.

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.

    Anti-word

    What this builds

    A five-letter daily puzzle with an original word list. The secret is a word for that day. The aim is not to find it quickly, but to make as many valid guesses as possible without hitting the secret or being boxed in. A guess is coloured against the secret. The run ends when the person types the secret, or when no valid unused word remains that fits the hints. A share line is produced. This is not someone else's game, and the lists are original.

    Read spekkr.inputs.json first. title labels the grid. day selects the secret from the list. list chooses the dictionary. hard tightens later guesses. keyboard adds on-screen keys.

    Out of scope

    • Someone else's word list, or a trademarked name in the UI.
    • A live 'today' that cannot be pinned in tests. The fixture day is always injectable.
    • Network, accounts, or a public streak server in the checks.

    Requirements

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

    R1. Lists and colouring
    • Guesses must be in the chosen list, five letters, A–Z, case-insensitive, stored uppercase.
    • Colouring is the standard mark against the secret: exact position, present but wrong place, or absent, with double-letter rules in design.md.
    • The secret for a day is list[(days since 2026-01-01) modulo list length]. For the fixture day 2026-01-15 with standard, the secret is the word in fixtures/day-2026-01-15.txt.

    Accept when: colouring fixtures in design.md all hold, a word not in the list is refused, and the fixture day secret matches the file.

    R2. The anti-word aim
    • A guess that is the secret ends the run as a 'caught' result, with the number of guesses made.
    • A guess that is valid and not the secret is accepted, coloured, and added to the grid.
    • The run is a 'lasted' result when the remaining unused list has no word that is consistent with all hints so far (and with hard notes, if on). The score is the number of guesses made.

    Accept when: the fixture run in design.md lasts 11 guesses and then has no consistent unused word; typing the secret on guess 3 is a caught result of 3.

    R3. Share text
    • A finished run produces a five-line share card: title, day, result (lasted 11 or caught in 3), and a row of colour marks per guess using the characters in design.md.
    • The exact fixture share text is fixtures/share-2026-01-15.txt.

    Accept when: the fixture run's share text matches the file byte for byte, including newlines.

    R4. Files
    • One command runs colouring, dictionary, fixture-day, and share-text tests, and writes the four screenshots. The clock is injected. No network.

    Accept when: the command passes for both lists and with hard on and off.

    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

    Colouring and dictionary tests cover exact, present, absent, and double letters. A known puzzle day is a fixture, never wall-clock 'today'. A scripted run lasts the documented number of guesses, and its share text matches a file byte for byte. The word lists are original. 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 pin a day, and how to run the checks.
    # Anti-word
    
    ## What this builds
    
    A five-letter daily puzzle with an original word list. The secret is a
    word for that day. The aim is not to find it quickly, but to make as many
    valid guesses as possible without hitting the secret or being boxed in. A
    guess is coloured against the secret. The run ends when the person types
    the secret, or when no valid unused word remains that fits the hints. A
    share line is produced. This is not someone else's game, and the lists are
    original.
    
    Read `spekkr.inputs.json` first. `title` labels the grid. `day` selects
    the secret from the list. `list` chooses the dictionary. `hard` tightens
    later guesses. `keyboard` adds on-screen keys.
    
    ## Out of scope
    
    - Someone else's word list, or a trademarked name in the UI.
    - A live 'today' that cannot be pinned in tests. The fixture day is always
      injectable.
    - Network, accounts, or a public streak server in the checks.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Lists and colouring
    
    - Guesses must be in the chosen list, five letters, A–Z, case-insensitive,
      stored uppercase.
    - Colouring is the standard mark against the secret: exact position,
      present but wrong place, or absent, with double-letter rules in
      `design.md`.
    - The secret for a day is `list[(days since 2026-01-01) modulo list
      length]`. For the fixture day 2026-01-15 with `standard`, the secret is
      the word in `fixtures/day-2026-01-15.txt`.
    
    Accept when: colouring fixtures in `design.md` all hold, a word not in the
    list is refused, and the fixture day secret matches the file.
    
    ### R2. The anti-word aim
    
    - A guess that is the secret ends the run as a 'caught' result, with the
      number of guesses made.
    - A guess that is valid and not the secret is accepted, coloured, and
      added to the grid.
    - The run is a 'lasted' result when the remaining unused list has no word
      that is consistent with all hints so far (and with hard notes, if on).
      The score is the number of guesses made.
    
    Accept when: the fixture run in `design.md` lasts 11 guesses and then has
    no consistent unused word; typing the secret on guess 3 is a caught result
    of 3.
    
    ### R3. Share text
    
    - A finished run produces a five-line share card: title, day, result
      (`lasted 11` or `caught in 3`), and a row of colour marks per guess
      using the characters in `design.md`.
    - The exact fixture share text is `fixtures/share-2026-01-15.txt`.
    
    Accept when: the fixture run's share text matches the file byte for byte,
    including newlines.
    
    ### R4. Files
    
    - One command runs colouring, dictionary, fixture-day, and share-text
      tests, and writes the four screenshots. The clock is injected. No
      network.
    
    Accept when: the command passes for both lists and with `hard` on and off.
    
    ### 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
    
    Colouring and dictionary tests cover exact, present, absent, and double
    letters. A known puzzle day is a fixture, never wall-clock 'today'. A
    scripted run lasts the documented number of guesses, and its share text
    matches a file byte for byte. The word lists are original. 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 pin a day, and how to run the checks.
    

    Open spec.md as plain text

  • design.md Colouring rules, the fixture day, and the share-text format.

    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.

    Colouring

    For each letter of the guess, left to right: if it matches the secret in that position, mark exact. Else if that letter still has unmatched occurrences in the secret (not already consumed by exact or earlier present marks), mark present. Else absent.

    The machine-checked colouring cases, including double letters, are fixtures/colouring.json. Tests compare to that file, not to a re-typed example.

    Fixture run (standard list, day 2026-01-15, hard off)

    The eleven guesses are fixtures/run-2026-01-15.txt, one word per line. After the eleventh, no unused consistent word remains. The share file is the authority for the card.

    Marks in the share text: exact is #, present is o, absent is ..

    Screenshot tolerance

    8 levels, 98% of pixels.

    Inputs

    KeyLabelDefaultNotes
    titleTitleLast as long as you canShown above the grid.
    dayPuzzle day2026-01-15A calendar date. The checks use this fixture day, never 'today' alone.
    hardHard notesoffA later guess must reuse every hint already given, in the anti-word sense described in design.md.
    keyboardOn-screen keyboardonLetter keys that pick up the hint colours.
    listWord liststandardstandard is the full original list. short is a 200-word fixture list for faster tests.

    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/colouring.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/day-2026-01-15.txtA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/run-2026-01-15.txtA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/share-2026-01-15.txtA 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/board.pngGuess four of a daily five-letter, played to last as long as possible.

    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. Colouring and dictionary tests cover exact, present, absent, and double letters. A known puzzle day is a fixture, never wall-clock 'today'. A scripted run lasts the documented number of guesses, and its share text matches a file byte for byte. The word lists are original. 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.
    
    ## Colouring
    
    For each letter of the guess, left to right: if it matches the secret in
    that position, mark `exact`. Else if that letter still has unmatched
    occurrences in the secret (not already consumed by `exact` or earlier
    `present` marks), mark `present`. Else `absent`.
    
    The machine-checked colouring cases, including double letters, are
    `fixtures/colouring.json`. Tests compare to that file, not to a re-typed
    example.
    
    ## Fixture run (standard list, day 2026-01-15, hard off)
    
    The eleven guesses are `fixtures/run-2026-01-15.txt`, one word per line.
    After the eleventh, no unused consistent word remains. The share file is
    the authority for the card.
    
    Marks in the share text: `exact` is `#`, `present` is `o`, `absent` is
    `.`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | Last as long as you can | Shown above the grid. |
    | `day` | Puzzle day | 2026-01-15 | A calendar date. The checks use this fixture day, never 'today' alone. |
    | `hard` | Hard notes | off | A later guess must reuse every hint already given, in the anti-word sense described in design.md. |
    | `keyboard` | On-screen keyboard | on | Letter keys that pick up the hint colours. |
    | `list` | Word list | standard | standard is the full original list. short is a 200-word fixture list for faster tests. |
    
    ## 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/colouring.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/day-2026-01-15.txt` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/run-2026-01-15.txt` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/share-2026-01-15.txt` | 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/board.png` | Guess four of a daily five-letter, played to last as long as possible. |
    
    
    ## 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. Colouring and dictionary tests cover exact, present, absent, and double
    letters. A known puzzle day is a fixture, never wall-clock 'today'. A
    scripted run lasts the documented number of guesses, and its share text
    matches a file byte for byte. The word lists are original. 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. Lists and colouring (R1). Build what R1. Lists and colouring asks for, to the numbers in design.md. In particular: Guesses must be in the chosen list, five letters, A–Z, case-insensitive, stored uppercase. Check: the R1. Lists and colouring acceptance checks pass.
    3. The anti-word aim (R2). Build what R2. The anti-word aim asks for, to the numbers in design.md. In particular: A guess that is the secret ends the run as a 'caught' result, with the number of guesses made. Check: the R2. The anti-word aim acceptance checks pass.
    4. Share text (R3). Build what R3. Share text asks for, to the numbers in design.md. In particular: A finished run produces a five-line share card: title, day, result (lasted 11 or caught in 3), and a row of colour marks per guess using the characters in design.md. Check: the R3. Share text acceptance checks pass.
    5. Files (R4). Build what R4. Files asks for, to the numbers in design.md. In particular: One command runs colouring, dictionary, fixture-day, and share-text tests, and writes the four screenshots. The clock is injected. No network. 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. **Lists and colouring (R1).** Build what `R1. Lists and colouring` asks
    for, to the numbers in `design.md`. In particular: Guesses must be in the
    chosen list, five letters, A–Z, case-insensitive, stored uppercase.
       Check: the `R1. Lists and colouring` acceptance checks pass.
    
    3. **The anti-word aim (R2).** Build what `R2. The anti-word aim` asks
    for, to the numbers in `design.md`. In particular: A guess that is the
    secret ends the run as a 'caught' result, with the number of guesses made.
       Check: the `R2. The anti-word aim` acceptance checks pass.
    
    4. **Share text (R3).** Build what `R3. Share text` asks for, to the
    numbers in `design.md`. In particular: A finished run produces a five-line
    share card: title, day, result (`lasted 11` or `caught in 3`), and a row
    of colour marks per guess using the characters in `design.md`.
       Check: the `R3. Share text` acceptance checks pass.
    
    5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in
    `design.md`. In particular: One command runs colouring, dictionary,
    fixture-day, and share-text tests, and writes the four screenshots. The
    clock is injected. No network.
       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/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

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.