# 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.