Break
Renders a component you choose under every scenario that can reach it on a temporary page and stress tests it.
Install
/plugin marketplace add jakubkrehel/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add jakubkrehel/skills --skill breakgit clone --depth 1 https://github.com/jakubkrehel/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/break ~/.claude/skills/breakPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Break This skill takes one component and renders it on a harness page under every scenario that can actually reach it. That page is the deliverable: a visual report the user scrolls through, every scenario on one page, with the breaks marked. It observes rather than judges. A finding here is something that visibly broke on the page, named in the vocabulary of the domain skill that owns the fix. Reviewing code against a standard is `interface-review` and `better-interface`; exploring design alternatives is `variant`; working through a component's product states one at a time is `state-machine`. Where `variant` insists on the real page, this skill isolates on purpose. You are not judging how the component looks in context. You are checking whether it defends itself when the content is worst-case. The whole run is build, look once, report: minutes, not a session. Nothing in it justifies instrumentation, browser debugging or a second pass. ## 1. Scope one component One component per run. "The settings page" is not a component; the profile form's text input is. Where the request spans several, list the candidates and ask which one to test. Restate what the component is in one sentence: what it accepts, what it renders and where it will live. ## 2. Infer the scenarios from the component
Details
- Skill name
break- Repository
- jakubkrehel/skills
- Path
skills/break/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Break skill do?
Renders a component you choose under every scenario that can reach it on a temporary page and stress tests it.
How do I install the Break skill?
Claude Code plugin: /plugin marketplace add jakubkrehel/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Break popular?
It lives in jakubkrehel/skills, which has 12,359 GitHub stars and 483 forks.
Related skills
Afk
12kjakubkrehel/skills
Works through a project while you're away, finding improvements and new ideas, building the best of them on a local branch and leaving a report for when you're back.
Better Accessibility
12kjakubkrehel/skills
Reviews and fixes keyboard and focus behavior, ARIA, accessible names, forms, screen-reader announcements, motion and zoom against WCAG 2.2.
Better Colors
12kjakubkrehel/skills
Builds and checks color systems by generating palettes, naming semantic tokens, converting between formats and measuring contrast.
Webcmd Browser
2.8kagentrhq/webcmd
Use when a live browser task requires Playwright interaction, authenticated handoff, visible UI verification, or ad-hoc page inspection.
Good Skill Complex
18klarksuite/cli
A very complex description that spans multiple lines and contains weird chars: !@#$%^&*()
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.