Jelly UI

Soft-body physics on ordinary form controls: a control still posts its value after a jiggle, with no NaNs, and a golden frame.

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

Build this spec

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

Jelly UI: heroJelly UI: loop

What can I customize?

Theme Colours, not the physics.

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.

    Jelly UI

    What this builds

    A form kit where buttons, sliders, and fields are soft bodies. They jiggle when dragged or clicked, but they remain ordinary controls: a submit still posts the values. Tests drag with a script, assert there are no NaNs, and assert the posted body. A golden animation frame is taken, settled or mid-jiggle at a pinned step. The look is original.

    Read spekkr.inputs.json first. title labels the fixture form. stiffness is the spring. theme is colour. wobble and labels change idle motion and chrome. Tests pin a seed and a step.

    Out of scope

    • A general physics engine demo unrelated to forms.
    • Network or a live form backend in the checks; posts are captured locally.
    • A claim of accessibility beyond the labelled controls and a documented keyboard path.

    Requirements

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

    R1. Values after a jiggle
    • The fixture form has a text field, a range, a checkbox, and a submit. A script fills them, drags each control as in fixtures/jelly-drag.json, then submits.
    • The posted body matches the object in the fixture file (name Ada, amount 7, agree true).
    • A keyboard path (tab, type, space, enter) also posts the same body, with no drag.

    Accept when: both the drag path and the keyboard path post the documented body.

    R2. Stability and frames
    • During the drag script, at every step, no vertex is NaN or infinite, and a button's centre stays within 80 px of its rest position.
    • Goldens: the rest form (wobble frozen), a mid-drag frame at the listed step, a settled frame 30 steps after release, and a 'posted' thank-you state.
    • One command runs the post tests, the NaN and bound checks, and writes the frames. No network.

    Accept when: the stability checks pass at stiffness 0.15 and 0.35, 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

    A control still posts its documented value after a scripted jiggle, and a keyboard path posts the same body. No NaNs occur under the drag script, and a button stays within a bound. A golden animation frame is checked at a pinned step. Posts are captured locally. 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 control, how to pin a seed, and how to run the checks.
    # Jelly UI
    
    ## What this builds
    
    A form kit where buttons, sliders, and fields are soft bodies. They jiggle
    when dragged or clicked, but they remain ordinary controls: a submit still
    posts the values. Tests drag with a script, assert there are no NaNs, and
    assert the posted body. A golden animation frame is taken, settled or
    mid-jiggle at a pinned step. The look is original.
    
    Read `spekkr.inputs.json` first. `title` labels the fixture form.
    `stiffness` is the spring. `theme` is colour. `wobble` and `labels` change
    idle motion and chrome. Tests pin a seed and a step.
    
    ## Out of scope
    
    - A general physics engine demo unrelated to forms.
    - Network or a live form backend in the checks; posts are captured
      locally.
    - A claim of accessibility beyond the labelled controls and a documented
      keyboard path.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Values after a jiggle
    
    - The fixture form has a text field, a range, a checkbox, and a submit. A
      script fills them, drags each control as in `fixtures/jelly-drag.json`,
      then submits.
    - The posted body matches the object in the fixture file (name Ada, amount
      7, agree true).
    - A keyboard path (tab, type, space, enter) also posts the same body, with
      no drag.
    
    Accept when: both the drag path and the keyboard path post the documented
    body.
    
    ### R2. Stability and frames
    
    - During the drag script, at every step, no vertex is NaN or infinite, and
      a button's centre stays within 80 px of its rest position.
    - Goldens: the rest form (wobble frozen), a mid-drag frame at the listed
      step, a settled frame 30 steps after release, and a 'posted' thank-you
      state.
    - One command runs the post tests, the NaN and bound checks, and writes
      the frames. No network.
    
    Accept when: the stability checks pass at stiffness 0.15 and 0.35, 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
    
    A control still posts its documented value after a scripted jiggle, and a
    keyboard path posts the same body. No NaNs occur under the drag script,
    and a button stays within a bound. A golden animation frame is checked at
    a pinned step. Posts are captured locally. 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 control, how to pin a seed, and how to run
      the checks.
    

    Open spec.md as plain text

  • design.md The fixture form, the drag script, and the posted body.

    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.

    Drag script

    Pointer moves are in the fixture file, in CSS pixels, at 1/60 s steps. The form's rest layout is 1600 by 1000.

    Screenshot tolerance

    8 levels, 98% of pixels, wobble frozen except the mid-drag frame (which is at a pinned step).

    Inputs

    KeyLabelDefaultNotes
    titleTitleA form that wobblesShown above the fixture form.
    stiffnessStiffness0.35From 0.15 to 0.8, the soft-body spring.
    wobbleIdle wobbleonA tiny motion at rest, seeded. Tests may freeze it.
    labelsShow labelsonOrdinary field labels.
    themeThemegelColours, not the physics.

    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/jelly-drag.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/form.pngA form mid-wobble, stiffness 0.35, values still Ada and still a form.

    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. A control still posts its documented value after a scripted jiggle, and a keyboard path posts the same body. No NaNs occur under the drag script, and a button stays within a bound. A golden animation frame is checked at a pinned step. Posts are captured locally. 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.
    
    ## Drag script
    
    Pointer moves are in the fixture file, in CSS pixels, at 1/60 s steps. The
    form's rest layout is 1600 by 1000.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels, wobble frozen except the mid-drag frame (which is
    at a pinned step).
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A form that wobbles | Shown above the fixture form. |
    | `stiffness` | Stiffness | 0.35 | From 0.15 to 0.8, the soft-body spring. |
    | `wobble` | Idle wobble | on | A tiny motion at rest, seeded. Tests may freeze it. |
    | `labels` | Show labels | on | Ordinary field labels. |
    | `theme` | Theme | gel | Colours, not the physics. |
    
    ## 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/jelly-drag.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/form.png` | A form mid-wobble, stiffness 0.35, values still Ada and still a form. |
    
    
    ## 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. A control still posts its documented value after a scripted jiggle, and
    a keyboard path posts the same body. No NaNs occur under the drag script,
    and a button stays within a bound. A golden animation frame is checked at
    a pinned step. Posts are captured locally. 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. Values after a jiggle (R1). Build what R1. Values after a jiggle asks for, to the numbers in design.md. In particular: The fixture form has a text field, a range, a checkbox, and a submit. A script fills them, drags each control as in fixtures/jelly-drag.json, then submits. Check: the R1. Values after a jiggle acceptance checks pass.
    3. Stability and frames (R2). Build what R2. Stability and frames asks for, to the numbers in design.md. In particular: During the drag script, at every step, no vertex is NaN or infinite, and a button's centre stays within 80 px of its rest position. Check: the R2. Stability and frames 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. **Values after a jiggle (R1).** Build what `R1. Values after a jiggle`
    asks for, to the numbers in `design.md`. In particular: The fixture form
    has a text field, a range, a checkbox, and a submit. A script fills them,
    drags each control as in `fixtures/jelly-drag.json`, then submits.
       Check: the `R1. Values after a jiggle` acceptance checks pass.
    
    3. **Stability and frames (R2).** Build what `R2. Stability and frames`
    asks for, to the numbers in `design.md`. In particular: During the drag
    script, at every step, no vertex is NaN or infinite, and a button's centre
    stays within 80 px of its rest position.
       Check: the `R2. Stability and frames` 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/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.