Art QR

A URL becomes a still-scannable poster or logo-embedded code: every fixture design decodes back to the input, with a golden poster.

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

Build this spec

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

Art QR: heroArt QR: loop

What can I customize?

Style poster is a large printed look. mark is logo-forward. plain is a bare code.

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.

    Art QR

    What this builds

    A designer for scannable codes that still look like a poster or a mark. A URL goes in; a picture comes out. Every fixture design must decode back to the input URL with a standard decoder. A golden poster is checked. The marks and the layouts are original. This is not a generator of confusing or malicious look-alike addresses; the payload is exactly the URL the person entered.

    Read spekkr.inputs.json first. title is on the poster around the code. url is the payload. style chooses a layout. logo and quiet change the mark and the margin.

    Out of scope

    • Encoding something other than a URL in this version.
    • A live shortener or a tracking redirect in the checks.
    • A claim of artistic copyright over the QR standard itself.

    Requirements

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

    R1. Decode
    • Each fixture in fixtures/art-qr.json (url, style, logo on or off, quiet on or off) renders an image that a standard decoder reads back as the exact URL, including scheme and case.
    • A deliberately broken fixture, with the logo covering too much, must fail the decode, so the test's decoder is known to work both ways.
    • The payload is the entered URL, not a shortened or rewritten address.

    Accept when: every good fixture decodes exactly, and the broken fixture fails to decode.

    R2. Frames and files
    • Goldens: a plain code, a poster with title, a logo-centre mark, and a tight quiet-off attempt that still decodes if the fixture says it should.
    • One command renders the fixtures, runs the decoder, and writes the frames. No network.

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

    Every fixture design decodes back to the exact input URL with a standard decoder. A broken, over-covered fixture fails, proving the decoder. A golden poster render is checked. No network and no URL rewriting.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to make a poster, how to run the decoder checks, and how large a logo may be.
    # Art QR
    
    ## What this builds
    
    A designer for scannable codes that still look like a poster or a mark. A
    URL goes in; a picture comes out. Every fixture design must decode back to
    the input URL with a standard decoder. A golden poster is checked. The
    marks and the layouts are original. This is not a generator of confusing
    or malicious look-alike addresses; the payload is exactly the URL the
    person entered.
    
    Read `spekkr.inputs.json` first. `title` is on the poster around the code.
    `url` is the payload. `style` chooses a layout. `logo` and `quiet` change
    the mark and the margin.
    
    ## Out of scope
    
    - Encoding something other than a URL in this version.
    - A live shortener or a tracking redirect in the checks.
    - A claim of artistic copyright over the QR standard itself.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Decode
    
    - Each fixture in `fixtures/art-qr.json` (url, style, logo on or off,
      quiet on or off) renders an image that a standard decoder reads back as
      the exact URL, including scheme and case.
    - A deliberately broken fixture, with the logo covering too much, must
      fail the decode, so the test's decoder is known to work both ways.
    - The payload is the entered URL, not a shortened or rewritten address.
    
    Accept when: every good fixture decodes exactly, and the broken fixture
    fails to decode.
    
    ### R2. Frames and files
    
    - Goldens: a plain code, a poster with title, a logo-centre mark, and a
      tight quiet-off attempt that still decodes if the fixture says it
      should.
    - One command renders the fixtures, runs the decoder, and writes the
      frames. No network.
    
    Accept when: the command passes, 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
    
    Every fixture design decodes back to the exact input URL with a standard
    decoder. A broken, over-covered fixture fails, proving the decoder. A
    golden poster render is checked. No network and no URL rewriting.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to make a poster, how to run the decoder checks, and
      how large a logo may be.
    

    Open spec.md as plain text

  • design.md Fixture designs, logo size, and the decode-back 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.

    Fixtures

    URLs use example.invalid and documentation-range hosts. The broken fixture uses a logo 60% of the code width. Good logo size is 15% of the code width, centred, with a light quiet ring.

    Screenshot tolerance

    8 levels, 98% of pixels for the poster chrome. Decode is exact.

    Inputs

    KeyLabelDefaultNotes
    titlePoster titleScan meDrawn on the poster, not inside the code if it would break scanning.
    urlDefault URLhttps://example.invalid/helloThe payload. Tests also inject fixture URLs.
    logoPlace a logo in the centreonA shipped mark, sized so the code still decodes.
    quietQuiet zoneonA four-module quiet zone. If off, tests may still require a decodable image, or may skip tight cases.
    styleStyleposterposter is a large printed look. mark is logo-forward. plain is a bare code.

    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/art-qr.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/poster.pngThe fixture poster for https://example.invalid/hello, still scannable, logo in the centre.

    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. Every fixture design decodes back to the exact input URL with a standard decoder. A broken, over-covered fixture fails, proving the decoder. A golden poster render is checked. No network and no URL rewriting.
    # 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.
    
    ## Fixtures
    
    URLs use `example.invalid` and documentation-range hosts. The broken
    fixture uses a logo 60% of the code width. Good logo size is 15% of the
    code width, centred, with a light quiet ring.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels for the poster chrome. Decode is exact.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Poster title | Scan me | Drawn on the poster, not inside the code if it would break scanning. |
    | `url` | Default URL | https://example.invalid/hello | The payload. Tests also inject fixture URLs. |
    | `logo` | Place a logo in the centre | on | A shipped mark, sized so the code still decodes. |
    | `quiet` | Quiet zone | on | A four-module quiet zone. If off, tests may still require a decodable image, or may skip tight cases. |
    | `style` | Style | poster | poster is a large printed look. mark is logo-forward. plain is a bare code. |
    
    ## 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/art-qr.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/poster.png` | The fixture poster for https://example.invalid/hello, still scannable, logo in the centre. |
    
    
    ## 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. Every fixture design decodes back to the exact input URL with a
    standard decoder. A broken, over-covered fixture fails, proving the
    decoder. A golden poster render is checked. No network and no URL
    rewriting.
    

    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. Decode (R1). Build what R1. Decode asks for, to the numbers in design.md. In particular: Each fixture in fixtures/art-qr.json (url, style, logo on or off, quiet on or off) renders an image that a standard decoder reads back as the exact URL, including scheme and case. Check: the R1. Decode 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: a plain code, a poster with title, a logo-centre mark, and a tight quiet-off attempt that still decodes if the fixture says it should. 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. **Decode (R1).** Build what `R1. Decode` asks for, to the numbers in
    `design.md`. In particular: Each fixture in `fixtures/art-qr.json` (url,
    style, logo on or off, quiet on or off) renders an image that a standard
    decoder reads back as the exact URL, including scheme and case.
       Check: the `R1. Decode` 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: a plain code, a
    poster with title, a logo-centre mark, and a tight quiet-off attempt that
    still decodes if the fixture says it should.
       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/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 QR decoder 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.