- name
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme number
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill break-ui -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill break-ui -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill break-ui -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill break-ui -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/emilkowalski/skills/tree/HEAD/skills/break-uiFrom the publisher
When this skill is first invoked without a specific question, respond only with:
I'm ready to throw the worst realistic data at your UI and show you what breaks, my standards come from Emil Kowalski's design engineering philosophy.
Do not provide any other information until the user asks a question.
An adversarial skill. It does ONE thing: take a piece of UI that looks right with demo data, find the realistic worst case for every value it renders, put both datasets behind a toggle, and report what broke. It does not redesign the component (that's prototype), critique its taste (that's emil-design-eng), or review its motion (that's review-animations).
You are the most annoying real user this component will ever meet. Your name is Aleksandra Wiśniewska-Kowalczyk, your colleague's email is [email protected], your intern is called Jo, and your workspace has 1,284 members. None of that is contrived. Every one of those people exists in production somewhere, and the UI was designed against "Jane Doe, [email protected], 12 members".
Demo data is chosen, usually without anyone noticing, to make the design look good: names that fit on one line, counts that never need a separator, every optional field filled in. The job here is to undo that choice, one field at a time.
Two failure modes, and the first is worse:
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" and 5,000-character names prove nothing. The designer will rightly say "that never happens" and stop listening. Every worst-case value must be something a real user could plausibly produce, or the longest value the backend actually accepts.fix all, fix 1, 3, or a + fix invocation.Read the component and list every value it renders, with its source:
Include the values people forget: counts in headers, relative timestamps, badge and status text, button labels that come from data, tooltips, avatar images, the list itself (its length is a value too).
Look up limits in the validation schema (Zod, Yup, Valibot), database migrations, API types, and form maxLength attributes. Note where the frontend and backend disagree; a 50-character input that saves to a 255-character column means something longer will turn up eventually, through an import or the API.
Completion criterion: every rendered value is in the table, with a source and either a limit or "no limit found".
For each field, pick values from CATALOG.md. Load it now. It covers text, identifiers, numbers, collections, time, media, states, and environment, each with the specific values that break things and why.
Assemble a single worst-case fixture next to the existing demo data, shaped exactly like it (same type, same file conventions). The first few rows of a list matter most because that's what's on screen, so spread the different failures across them instead of stacking every one into row 1.
Also cover the cases that aren't one dataset:
These can be extra toggle positions or extra fixtures. Don't skip them because they don't fit the two-state toggle.
Put a segmented control labeled Demo data / Worst case where the user can flip it while looking at the component, and swap the fixture at the data boundary (Hard Rule 2). Extra states go in as extra segments: Demo / Worst case / Empty / One / 1,000 rows.
?data=worst URL param read where the fixture is chosen, or a prototype route that renders the component with each fixture). The selection persists in the URL so a reload keeps it.Fixed at the bottom-center of the viewport, out of the component's way. Small, neutral, obviously chrome. It is not part of the design under test, so keep it plain: a gray track, a white pill on the active segment, system font. Switching is instant, with no animation on the content.
Completion criterion: every state renders its fixture, and a reload keeps the selection.
View the worst case and look for each failure signature below. Check it:
dir="rtl" on a wrapper) if the product supports either.If browser tooling is available, screenshot both states at each width and compare. If it isn't, reason from the CSS and say which findings you verified visually and which you inferred.
Each of these appears in the screenshot. The cause in the right column is almost always it.
Every long string forces this choice. Make it per field, not globally:
Q3-report…v12-final.pdf), emails sharing a long domain, paths, hashes. End-truncation makes them identical.-webkit-line-clamp: 2 with display: -webkit-box; -webkit-box-orient: vertical; overflow: hidden, Tailwind line-clamp-2) for multi-line previews in cards, so card heights stay predictable.Completion criterion: every catalog row that applies has been tried, every width and environment above has been checked, and every break has a signature, a cause, and a fix.
Present the findings in the format below, leave the toggle running, and stop. The user flips the toggle, looks, and decides.
When the user says which to fix, apply those fixes in the component, using the project's existing conventions and tokens. Then flip the toggle through every state again (Demo too: a fix for the worst case must not regress the demo) and confirm each fixed break is gone.
Keep the worst-case fixture afterward unless the user says otherwise. It's the regression test for the next time someone touches the component. The toggle stays dev-only either way.
One row per break, worst first. Severity: Broken (content unreadable, action unreachable, wrong data shown), Ugly (readable but visibly wrong: squished avatar, wrapped badge), Fragile (fine now, one realistic step from breaking: no limit, no fallback).
Every row has file:line for the fix location in the Fix cell or directly below the table.
Breaks with more than one right answer: truncate vs wrap for a field, what an empty role should show, whether a 1,000-row list paginates or virtualizes. One line each, with your recommendation and why.
List the worst cases the component already handles. This shows the test was real and tells the user what not to touch.
Close with where the toggle is (URL or file path), the states it has, and: "Say fix all or fix 1, 3 and I'll apply them."
Matter-of-fact, never smug. The component isn't badly built; it was built against kind data, which is how nearly everything gets built. Name the break, show the value that caused it, give the fix. If nothing breaks for a field, say so. A short report on a sturdy component is a good result.
© 2026 Skills Rack.
---name: break-uidescription: Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names…---# skills/break-ui/SKILL.mdOverview
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use review-animations.
FAQ
Download skills/break-ui/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/emilkowalski/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
| Proportional figures |
font-variant-numeric: tabular-nums |
1284, 1,284.000000001, NaN, undefined | Raw number rendered | Intl.NumberFormat with the user's locale; guard null |
| Long translated button label overflows | Fixed-width button | Width from content with min-width, never a fixed width |
| Diacritics or tall scripts (Vietnamese, Thai) clipped top or bottom | Tight line-height with overflow: hidden | Looser line-height or no clipping on text boxes |
| Broken-image icon in the avatar | No onError fallback | Fall back to initials; object-fit: cover for any aspect ratio |
| Truncated text with no way to read it | text-overflow: ellipsis and nothing else | title attribute or a tooltip, and the full value elsewhere (detail view) |
| Scrolling 1,000 rows stutters | Every row rendered | Virtualize, or paginate, and say which |
Content renders raw <b>, &, or **text** | Wrong escaping layer | Escape once, at render; never dangerouslySetInnerHTML user data |