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