Skip to content
SkillModel-led3,419 tokens in use

break-ui

Stress-tests a component with worst-case data such as long names, empty lists and emoji, behind a dev-only toggle, and reports every break with a fix.

58,388 stars on the repository MIT Licenseemilkowalski/skills · skills/break-ui
npx skills@latest add emilkowalski/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing break-ui costs

122tokens idle
3,419tokens in use
5,636tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples6/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance40
  • Community52
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers