Break: Component Stress Test
Render a chosen component in a temporary page under relevant stress scenarios.
These skills help an agent exercise a real app in a browser and catch broken flows. They include Playwright tooling, component stress and state tests, and dogfooding workflows.
10 skillsRender a chosen component in a temporary page under relevant stress scenarios.
Stress-test UI components with realistic edge-case data and a switchable worst-case fixture.
Automate browser interactions, inspect pages and work with Playwright tests through the official Playwright CLI.
Check shipped packages, deployments, installed plugins, and late reports during a defined post-release observation window.
Render a component’s states on a temporary page with mock data and a switcher.
Compare a rendered page with a change baseline and report newly introduced, resolved and pre-existing accessibility issues.
Use Playwright to inspect local web apps, exercise frontend flows and capture screenshots and logs.
Turn browser tasks into reusable Playwright scripts for navigation, screenshots, form interactions, responsive checks, and link inspection.
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match.
Systematically explore and test a web application to find bugs, UX issues, and other problems.
Choose a testing Skill for local web app flows, browser interactions or headless Godot test suites.
Use Playwright skills for repeatable end-to-end runs, and stress or dogfood skills for exploratory checks.