playwright-setuplisted

# Playwright Setup Generator ## Goal Produce a complete, ready-to-run Playwright E2E test suite for any project by: 1. Mining existing docs and source code for user flows 2. Interviewing the user to fill gaps and confirm scope 3. Presenting a test plan for approval 4. Writing all required files Do NOT write any files until the user approves the plan. --- ## Phase 1 — Document Discovery Scan in this order. Stop at each level if enough info found to draft a plan. ### Level 1: Requirements docs (highest signal) Check these paths (adapt to project root): ``` Documentation/Product/Product-Requirements-Document.md Documentation/Product/User-Journey-Document.md Documentation/Product/Feature-Ticket-List.md docs/PRD.md docs/requirements.md docs/user-stories.md README.md FEATURES.md ``` Also check `graphify-out/GRAPH_REPORT.md` if it exists — it shows god nodes (most-connected features) and community clusters which map directly to test suites. ### Level 2: Source code scan (if docs sparse) Scan the project source for: | Signal | Where to look | What it tells you | |--------|---------------|-------------------| | Routes / pages | `src/router/`, `src/pages/`, `app/`, `pages/` | User-navigable flows | | API endpoints | `src/routes/`, `controllers/`, `api/` | Backend features to test | | Auth flows | `login`, `register`, `auth` in filenames | Login/logout/session tests | | Forms | `<form>`, `v-model`, `useForm`, `handleSubmit` in source | Input validation tests | | User roles |