break

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 code review misses. This Skill stress-tests a single component by rendering it under every scenario that can actually reach it, producing a visual report 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 curated scenario catalog. - Harness Page Generation: Builds one throwaway page that imports the real component untouched and renders it once per scenario in a single column with labels, using the app's own layout, fonts, and tokens. - Findings Report: Marks each visible break on the page and reports a table mapping broken scenarios to the domain skill that owns the fix, such as better-typography or better-layout. - Use Case: Before shipping a new profile form input, render it with empty strings, 60-character unbreakable URLs, RTL text, and a 320px container to catch overflow and truncation issues in minutes. ## Quick Start Ask the assistant to run the break skill on a specific component, for example: stress test the UserCard component and show me every state where it breaks.