dogfood

Provide a target URL, a testing scope such as specific features or full site, and optionally an output directory. The Skill follows a 5-phase workflow: plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues, and generate a report.

Call browser_console after every navigation and significant interaction to capture uncaught exceptions, failed network requests, and deprecation warnings. Silent console errors are classified as high-value findings in the issue taxonomy.

This workflow requires a browser toolset providing browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. Without these tools the testing phases cannot execute.

Issues are rated Critical, High, Medium, or Low based on impact, from broken core features down to minor polish issues. Each issue also gets a category: Functional, Visual, Accessibility, Console, UX, or Content, defined in the issue taxonomy reference.

Testing is limited to what the browser toolset can reach and observe; areas behind unavailable credentials or blocked flows are recorded as blockers in the report. It does not execute load testing, API-level testing, or deep security scanning.