What problem does it solve? Manual exploratory QA of web applications is time-consuming and inconsistent, often missing silent JavaScript errors, broken flows, and visual defects. This Skill systematizes the process by driving a browser through the application, capturing evidence, and producing a structured bug report. ## Core Features & Use Cases - Five-phase QA workflow: Plan, Explore, Collect Evidence, Categorize, and Report, covering navigation, forms, keyboard input, scrolling, and edge cases. - Evidence capture: Takes annotated screenshots, records console errors, and documents reproduction steps for every issue found. - Standardized classification: Uses a severity (Critical/High/Medium/Low) and category (Functional/Visual/Accessibility/Console/UX/Content) taxonomy, then generates a report from a Markdown template. - Use Case: Point it at a staging URL before a release; it clicks through sign-up, login, and checkout flows, flags a broken submit button and console exceptions, and delivers a prioritized report with screenshots. ## Quick Start Run exploratory QA on https://staging.example.com covering the full site and save the report and screenshots to ./dogfood-output.