What problem does it solve? Components built against one happy path look finished until real content arrives: long strings, empty states, narrow containers, and error states expose breaks that normal development never shows. This Skill stress tests a single component by rendering it in every realistic scenario on one temporary page. ## Core Features & Use Cases - Scenario Inference: Reads the component's props, slots, and states, then selects only the applicable stress axes (content length, content shape, quantity, container width, state, environment) from a defined scenario catalog. - Harness Page Generation: Builds a throwaway page that imports the real component untouched, rendering one instance per scenario in fixed-width containers with labels. - Visual Break Reporting: Produces a findings table of observed breaks, each assigned to the owning domain skill (better-typography, better-layout, better-accessibility, and others) so fixes start in the right place. - Use Case: Before shipping a new profile form input, render it with empty strings, 60-character unbreakable URLs, RTL text, zero items, and a 320px container to catch overflow and missing empty states in one page load. ## Quick Start Ask the agent to run the break skill on a specific component, for example: stress test the UserCard component against worst-case content and show me what breaks.