test-setup

Scaffold the project's test infrastructure from the approved QA plan before any feature tests are written. Non-autonomous: present the full plan, get approval, then execute. Never install packages or write config files without sign-off.

Phases

1. Load context — read docs/specs/qa-plan.md to understand the chosen pyramid and tooling decisions. If the file is missing, stop and direct to /qa-plan. Also read package.json and any existing test config files to avoid duplicating setup.
2. Present the plan — show the user the EXACT commands and files that will be created, including: install commands for Vitest, @testing-library/react, @testing-library/jest-dom, @playwright/test, and any supporting packages (jsdom, @vitejs/plugin-react — or @vitejs/plugin-react-swc for Next.js projects that use the SWC compiler; both require jsdom as the Vitest test environment, etc.); a Playwright browser-binary install step (npx playwright install --with-deps) that runs after @playwright/test is installed, so that npm run test:e2e does not fail with a missing-browser error; config files to be written (vitest.config.ts, vitest.setup.ts, playwright.config.ts); package.json scripts to be added (test, test:watch, test:e2e); and the CI test step (e.g. a GitHub Actions job snippet). Under full, confirm each category; under lean, one confirmation for the whole plan; under solo, proceed directly. Get explicit approval before running anything.
3. Apply — on approval, run the install commands (including npx playwright install --with-deps), write the config files, and add the package.json scripts. Then add one trivial smoke test — place it under __tests__/ colocated with the app (e.g. src/__tests__/smoke.test.ts, or at the project root __tests__/smoke.test.ts if there is no src/ directory) — rendering a minimal component, and one Playwright homepage test (e2e/smoke.spec.ts visiting /) to verify the harness end-to-end.
4. Verify — run npm test (or equivalent) and npm run test:e2e against the smoke tests; show the output. If anything fails, diagnose and fix before proceeding. Under full, confirm each suite result; under lean or solo, summarize the combined result.
5. Next step — on a green run, point to /write-tests.

Output

A runnable test scaffold: Vitest + Testing Library config, Playwright config, two smoke tests, updated package.json scripts, and a CI test step snippet. No application code is modified.