Dogfood Skill

Systematic exploratory QA of a web application: navigate it, interact with it, capture evidence of anything broken, and produce a structured bug report with screenshots and console errors attached.

This skill drives a real headless Chromium instance through a small bundled Node script (scripts/browser-driver.mjs). One browser session stays alive across the whole pass, so pages, cookies, and console history persist. It requires filesystem access, a shell, Node/npm, and Chromium. Use a native browser tool instead when it supports the required navigation, evidence, console, and axe operations.

Setup: paths & shell state (READ THIS FIRST)

Two facts about how commands run, and how this skill deals with them:

1. Each Bash command may run in a fresh shell. Shell variables and exports do not carry over from one Bash call to the next. So this skill does not rely on a variable set in an earlier step. Instead:
   • The output directory is a fixed relative path, ./dogfood-output — the working directory (your project root) is stable between calls, so this same relative path always resolves to the same place. Every command below uses it literally.
   • The one value that must be absolute is this skill's own directory (where browser-driver.mjs lives). Each Bash block that needs it sets D= on its first line. You must fill in D with the real absolute path (see step 2). Do not leave the placeholder.