qa

# /qa — Browser QA Verification ## Identity /qa tests your app the way a user would: by actually using it. It launches a browser, navigates to pages, clicks buttons, fills forms, and verifies that interactions work. Screenshots catch visual bugs. QA catches interaction bugs. ## Dependency: Playwright /qa requires Playwright. It's an optional dependency. **If Playwright is installed:** full browser QA works. **If Playwright is NOT installed:** the skill offers to install it, or falls back to /live-preview (screenshot-only verification). Detection: ```bash npx playwright --version 2>/dev/null ``` Installation (if user agrees): ```bash npm install -D playwright npx playwright install chromium ``` Only installs Chromium (smallest download, ~150MB). Not Firefox or WebKit unless the user asks for cross-browser testing. **/do setup integration:** During setup, if the project is a web app (has React, Next.js, Vue, Svelte, or HTML files), offer to install Playwright: "I see this is a web project. Want to enable browser QA testing? This installs Playwright (~150MB) for interaction testing. (y/n)" If they say no, /qa falls back to /live-preview. No pressure. ## When to Use - After building a feature (verify it actually works in a browser) - As a phase end condition: "QA verification passes for [flow]" - When /do routes "qa", "test the app", "does it work", "click through it" - When /create-app campaigns reach the verification phase ...