Break UI takes a piece of UI that looks right with demo data and finds the realistic worst case for every value it renders. It puts both datasets behind a Demo data or Worst case toggle, looks for overflow, truncation and layout failures, and reports each one with a proposed fix. It reports first and edits only when asked.
What You Get
- A worst-case dataset built from realistic values or the real schema limits
- A dev-only toggle between demo data and worst-case data
- A list of what broke with a proposed fix for each
- Optional fixes applied on request, for all or selected items
Common Use Cases
- Testing a user list with long names and unbreakable emails
- Checking empty, zero and huge-count states of a dashboard card
- Finding truncate, wrap or clamp decisions in a table
What Makes It Unique
The worst case enters through the same boundary as the demo data, such as the fixture, the mock or the props, so the test exercises the component and leaves its markup unedited. A single dataset hits many failure types at once, limits come from schemas where they exist, and a missing limit is reported as a finding.
Under The Hood
A SKILL.md plus one more reference file. The model reads the component and its data source, edits a fixture or adds a dev-only switch such as a URL parameter, renders the component with each dataset and writes a report. It treats repository content as data and flags text that tries to steer it.