Performative UI

A kit of ironic interface tropes, each checked at documented states, plus a composition page screenshot.

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

Build this spec

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

Performative UI: heroPerformative UI: loop

What can I customize?

Density How tight the composition page is.

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.

    Performative UI

    What this builds

    A component kit of design clichés: glass panels, a lush gradient hero, a row of badges, a glowing border, a fake 'intelligent' purple button. The kit is both the joke and a usable library. Each trope has documented states (rest, hover, disabled) and a visual-regression frame. A composition page puts them together. The names and the CSS are original; no third-party kit is required.

    Read spekkr.inputs.json first. title and brand appear on the composition page. density changes spacing. motion and dark change the stage.

    Out of scope

    • A full application design system with data tables and forms beyond the tropes listed.
    • Network or a live theme marketplace.
    • A claim that these tropes are good taste.

    Requirements

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

    R1. Tropes and states
    • The tropes are listed in design.md, each with the states rest, hover, and disabled where they apply.
    • A visual-regression frame of each trope at each documented state matches a golden, with motion frozen at t = 0.
    • The composition page, with title and brand, matches composition at the chosen density.

    Accept when: every listed trope/state golden matches, and the composition matches.

    R2. Files
    • One command builds the kit, takes the frames (including four named shots: glass, a gradient hero, a badge row, and the composition), and compares them. No network.

    Accept when: the command passes at both densities, with motion on (frozen) and off.

    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

    Visual regression covers each trope at documented states, motion frozen. A composition page screenshot is checked. No third-party kit 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 use a trope, how to add one, and how to run the checks.
    # Performative UI
    
    ## What this builds
    
    A component kit of design clichés: glass panels, a lush gradient hero, a
    row of badges, a glowing border, a fake 'intelligent' purple button. The
    kit is both the joke and a usable library. Each trope has documented
    states (rest, hover, disabled) and a visual-regression frame. A
    composition page puts them together. The names and the CSS are original;
    no third-party kit is required.
    
    Read `spekkr.inputs.json` first. `title` and `brand` appear on the
    composition page. `density` changes spacing. `motion` and `dark` change
    the stage.
    
    ## Out of scope
    
    - A full application design system with data tables and forms beyond the
      tropes listed.
    - Network or a live theme marketplace.
    - A claim that these tropes are good taste.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Tropes and states
    
    - The tropes are listed in `design.md`, each with the states `rest`,
      `hover`, and `disabled` where they apply.
    - A visual-regression frame of each trope at each documented state matches
      a golden, with motion frozen at t = 0.
    - The composition page, with `title` and `brand`, matches `composition` at
      the chosen density.
    
    Accept when: every listed trope/state golden matches, and the composition
    matches.
    
    ### R2. Files
    
    - One command builds the kit, takes the frames (including four named
      shots: glass, a gradient hero, a badge row, and the composition), and
      compares them. No network.
    
    Accept when: the command passes at both densities, with motion on (frozen)
    and off.
    
    ### 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
    
    Visual regression covers each trope at documented states, motion frozen. A
    composition page screenshot is checked. No third-party kit 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 use a trope, how to add one, and how to run the
      checks.
    

    Open spec.md as plain text

  • design.md The trope list, states, and composition goldens.

    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.

    Tropes

    glass-panel, gradient-hero, glow-border, badge-row, intelligent-button, pill-nav, mesh-backdrop. States and any text they contain are fixtures/tropes.json. Goldens live under goldens/tropes/.

    Screenshot tolerance

    8 levels, 98% of pixels, 1600 by 1000, frozen motion.

    Inputs

    KeyLabelDefaultNotes
    titleTitle on the composition pageA page of tropesShown at the top of the composition.
    brandBrand wordAURORAUsed on badges and a fake wordmark.
    motionAllow motiononIf off, tropes that pulse or shimmer are frozen at t = 0.
    darkDark stageonA dark backdrop for the kit.
    densityDensityairyHow tight the composition page is.

    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/tropes.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/tropes.pngThe AURORA composition page: cookie wall, notifications, a skeuomorph.

    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. Visual regression covers each trope at documented states, motion frozen. A composition page screenshot is checked. No third-party kit 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.
    
    ## Tropes
    
    `glass-panel`, `gradient-hero`, `glow-border`, `badge-row`,
    `intelligent-button`, `pill-nav`, `mesh-backdrop`. States and any text
    they contain are `fixtures/tropes.json`. Goldens live under
    `goldens/tropes/`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels, 1600 by 1000, frozen motion.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title on the composition page | A page of tropes | Shown at the top of the composition. |
    | `brand` | Brand word | AURORA | Used on badges and a fake wordmark. |
    | `motion` | Allow motion | on | If off, tropes that pulse or shimmer are frozen at t = 0. |
    | `dark` | Dark stage | on | A dark backdrop for the kit. |
    | `density` | Density | airy | How tight the composition page is. |
    
    ## 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/tropes.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/tropes.png` | The AURORA composition page: cookie wall, notifications, a skeuomorph. |
    
    
    ## 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. Visual regression covers each trope at documented states, motion
    frozen. A composition page screenshot is checked. No third-party kit 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. Tropes and states (R1). Build what R1. Tropes and states asks for, to the numbers in design.md. In particular: The tropes are listed in design.md, each with the states rest, hover, and disabled where they apply. Check: the R1. Tropes and states acceptance checks pass.
    3. Files (R2). Build what R2. Files asks for, to the numbers in design.md. In particular: One command builds the kit, takes the frames (including four named shots: glass, a gradient hero, a badge row, and the composition), and compares them. No network. Check: the R2. 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. **Tropes and states (R1).** Build what `R1. Tropes and states` asks
    for, to the numbers in `design.md`. In particular: The tropes are listed
    in `design.md`, each with the states `rest`, `hover`, and `disabled` where
    they apply.
       Check: the `R1. Tropes and states` acceptance checks pass.
    
    3. **Files (R2).** Build what `R2. Files` asks for, to the numbers in
    `design.md`. In particular: One command builds the kit, takes the frames
    (including four named shots: glass, a gradient hero, a badge row, and the
    composition), and compares them. No network.
       Check: the `R2. 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/InstrumentSans.ttf Instrument Sans variable typeface for the reference preview.
  • reference/fonts/InstrumentSerif.ttf Instrument Serif for the reference preview.
  • reference/fonts/InstrumentSerif-Italic.ttf Instrument Serif italic for the reference preview.

Is it for me?

Platforms
web
Tools
TypeScript, CSS

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.