Mentioned books

A shelf of books mentioned in a community, searched over a fixture corpus, with a golden shelf page and no live scrape in CI.

This is a small site 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/mentioned-books
Version
0.2.1
Published by
lume
Updated
15 Nov 2026

Build this spec

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

Mentioned books: hero

What can I customize?

Corpus A shipped mention log. No live scrape.

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.

    Mentioned books

    What this builds

    A shelf of books drawn from a community's mentions. The mentions are a fixture corpus: a title, a count, a date, a short quote. Search and listing run over that corpus. Checks do not scrape a live community. A golden shelf page is taken. Titles in the sample corpus are used as mentions, with care for rights in the quotes (short, attributed, or invented).

    Read spekkr.inputs.json first. title labels the shelf. query is the first search. corpus chooses the log. counts and blurbs change the cards.

    Out of scope

    • A live scrape of a forum, a shop, or a social site in the checks.
    • A paid book API in the checks.
    • A claim of official sales rank.

    Requirements

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

    R1. Search and listing
    • The sample corpus is fixtures/mentions-sample.json. A search for river returns the documented list, in the sort order in the file (usually count descending).
    • An empty query lists the top N (20) by count. A query with no hit shows an empty state.
    • A fetch hook fails if a live community or shop host is contacted.

    Accept when: the river list, the top-20, and the empty state match, and the hook stays quiet.

    R2. Frames and files
    • Goldens: the default shelf (top), the river search, a book card, and the tiny corpus.
    • One command runs the searches, the hook, and writes the frames. No network.

    Accept when: the command passes for both corpora, and the frames match the goldens.

    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

    Search and listing run over a fixture corpus and match documented result lists. A golden shelf page is checked. A fetch hook fails if a live community is scraped. No shop API and no network are required.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to add a mention record, how quotes are handled, and how to run the checks.
    # Mentioned books
    
    ## What this builds
    
    A shelf of books drawn from a community's mentions. The mentions are a
    fixture corpus: a title, a count, a date, a short quote. Search and
    listing run over that corpus. Checks do not scrape a live community. A
    golden shelf page is taken. Titles in the sample corpus are used as
    mentions, with care for rights in the quotes (short, attributed, or
    invented).
    
    Read `spekkr.inputs.json` first. `title` labels the shelf. `query` is the
    first search. `corpus` chooses the log. `counts` and `blurbs` change the
    cards.
    
    ## Out of scope
    
    - A live scrape of a forum, a shop, or a social site in the checks.
    - A paid book API in the checks.
    - A claim of official sales rank.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Search and listing
    
    - The sample corpus is `fixtures/mentions-sample.json`. A search for
      `river` returns the documented list, in the sort order in the file
      (usually count descending).
    - An empty query lists the top N (20) by count. A query with no hit shows
      an empty state.
    - A fetch hook fails if a live community or shop host is contacted.
    
    Accept when: the river list, the top-20, and the empty state match, and
    the hook stays quiet.
    
    ### R2. Frames and files
    
    - Goldens: the default shelf (top), the river search, a book card, and the
      tiny corpus.
    - One command runs the searches, the hook, and writes the frames. No
      network.
    
    Accept when: the command passes for both corpora, and the frames match the
    goldens.
    
    ### 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
    
    Search and listing run over a fixture corpus and match documented result
    lists. A golden shelf page is checked. A fetch hook fails if a live
    community is scraped. No shop API and no network are required.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to add a mention record, how quotes are handled, and
      how to run the checks.
    

    Open spec.md as plain text

  • design.md The fixture corpus, search order, and the no-scrape rule.

    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.

    Sample corpus

    At least 30 mention records: title, optional author, count, last-mentioned date, a short quote. The river query's expected ids are in fixtures/search-river.json.

    Screenshot tolerance

    8 levels, 98% of pixels. The listed titles must also match the file.

    Inputs

    KeyLabelDefaultNotes
    titleTitleBooks people mentionedShown above the shelf.
    queryDefault queryriverUsed on first load. Tests also inject queries.
    countsShow mention countsonA number next to each title, from the corpus.
    blurbsShow a short blurbonA shipped blurb, not a live blurb API.
    corpusCorpussampleA shipped mention log. No live scrape.

    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/mentions-sample.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/search-river.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/shelf.pngSearch “river” on the fixture corpus, a golden shelf and list.

    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. Search and listing run over a fixture corpus and match documented result lists. A golden shelf page is checked. A fetch hook fails if a live community is scraped. No shop API and no network are required.
    # 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.
    
    ## Sample corpus
    
    At least 30 mention records: title, optional author, count, last-mentioned
    date, a short quote. The river query's expected ids are in
    `fixtures/search-river.json`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. The listed titles must also match the file.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | Books people mentioned | Shown above the shelf. |
    | `query` | Default query | river | Used on first load. Tests also inject queries. |
    | `counts` | Show mention counts | on | A number next to each title, from the corpus. |
    | `blurbs` | Show a short blurb | on | A shipped blurb, not a live blurb API. |
    | `corpus` | Corpus | sample | A shipped mention log. No live scrape. |
    
    ## 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/mentions-sample.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/search-river.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/shelf.png` | Search “river” on the fixture corpus, a golden shelf and list. |
    
    
    ## 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. Search and listing run over a fixture corpus and match documented
    result lists. A golden shelf page is checked. A fetch hook fails if a live
    community is scraped. No shop API and no network are required.
    

    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. Search and listing (R1). Build what R1. Search and listing asks for, to the numbers in design.md. In particular: The sample corpus is fixtures/mentions-sample.json. A search for river returns the documented list, in the sort order in the file (usually count descending). Check: the R1. Search and listing acceptance checks pass.
    3. Frames and files (R2). Build what R2. Frames and files asks for, to the numbers in design.md. In particular: Goldens: the default shelf (top), the river search, a book card, and the tiny corpus. Check: the R2. Frames and files 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. **Search and listing (R1).** Build what `R1. Search and listing` asks
    for, to the numbers in `design.md`. In particular: The sample corpus is
    `fixtures/mentions-sample.json`. A search for `river` returns the
    documented list, in the sort order in the file (usually count descending).
       Check: the `R1. Search and listing` acceptance checks pass.
    
    3. **Frames and files (R2).** Build what `R2. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: the default shelf
    (top), the river search, a book card, and the tiny corpus.
       Check: the `R2. Frames and files` 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/Newsreader.ttf Newsreader variable typeface for the reference preview.
  • reference/fonts/Newsreader-Italic.ttf Newsreader 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.115 Nov 2026Names what it builds.
  • 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.