agentleFS
aipphilieaipphilie/claude-skills/.claude/skills/break-ui/SKILL.md

break-ui

Skill0 starsChanged 19 days agoNo licenceView on GitHub

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.

31 other projects use a version of this, 17 of them edited; 11 of 16 edited versions we compared changed its rules; 6 new projects in the last 4 weeks, against 2 the 4 before.

How people change it

11 of 16 edited versions changed its rules, and some changes recur.

Of the 16 edited versions we compared: 3 keep every rule, 2 are an older text, 11 made changes of their own.

Not in older versions

  1. A rule we can't quote: its licence doesn't allow itmissing from 2 of 2
  2. A rule we can't quote: its licence doesn't allow itmissing from 2 of 2

Rules people drop

  1. A rule we can't quote: its licence doesn't allow itdropped by 5 of 11
  2. A rule we can't quote: its licence doesn't allow itdropped by 5 of 11
  3. A rule we can't quote: its licence doesn't allow itdropped by 3 of 11
  4. A rule we can't quote: its licence doesn't allow itdropped by 3 of 11
  5. A rule we can't quote: its licence doesn't allow itdropped by 3 of 11
  6. A rule we can't quote: its licence doesn't allow itdropped by 3 of 11
  7. A rule we can't quote: its licence doesn't allow itdropped by 3 of 11
  8. A rule we can't quote: its licence doesn't allow itdropped by 3 of 11

Rules people add

  1. Completion criterion: every state renders its fixture, and a reload keeps the selection.added by 7 of 11
  2. A rule we can't quote: its licence doesn't allow itadded by 3 of 11
  3. Look for each signature below:added by 2 of 11
  4. Truncate in the middle when items differ at the end (file names, SKUs sharing a prefix).added by 2 of 11

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 6 new projects took it in the last 4 weeks, 3× the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 1 new projectWeek of Oct 18: 3 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 1 new projectWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 8 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use remove-animations, learn-taste and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • boraoztuncSkill

    remove-animations

    Find the animations an interface doesn't need and remove them — motion on keyboard actions, high-frequency surfaces, functional data, and decoration with no purpose — then clean up what they leave behind. Edits code, but only to subtract; it never adds or retunes motion. Use when the user says the app "feels slow", "has too much animation", "feels over-animated", wants to "tone down the motion", or asks what animations to remove. For finding places that should animate, use find-animation-opportunities; for fixing animations that should stay, use improve-animations or review-animations.

    Also in 10 projects that use this

  • boraoztuncSkill

    learn-taste

    Turn a session's design corrections into rules, with their why, in DESIGN.md, a project skill, or a lint check.

    Also in 7 projects that use this

  • emilkowalskiSkill

    ask-emil

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 4 projects that use this

  • +2 more from boraoztunc

The file

We split this skill into the rules it gives an agent

12 rules. 8 are common, 2 are distinctive, and 2 are very specific to this project.

  • 8

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.