playwright-e2e-builder

Topics in the source

• Playwright E2E Test Suite Builder
• When to use
• Phase 1: Explore (Plan Mode)
• Project structure
• Application structure
• CI/CD
• Phase 2: Interview (AskUserQuestion)
• Round 1: Scope and critical flows

Use this skill when you need to: Set up Playwright from scratch in an existing project Build E2E tests for critical user flows (signup, checkout, dashboards) Implement Page Object Model for maintainable test architecture Configure authentication state persistence across tests Set up visual regression testing with screenshots Integrate Playwright into CI/CD with sharding and retries Enter plan mode. Before writing any tests, explore the existing project: Find the tech stack: is this React, Next.js, Vue, SvelteKit, or another framework? Check if Playwright is already installed (playwright.config.ts, @playwright/test in package.json) Look for existing test directories (e2e/, tests/, tests/) Check for existing E2E tests in Cypress, Selenium, or other frameworks (migration context) Find the dev server command and port (npm run dev, next dev, etc.) Identify the main routes/pages (look at router config, pages directory, or route files) Find authentication flow (login page URL, auth API endpoints, token storage) Check for test IDs in components (data-testid, data-test, data-cy attributes) Look for API routes that tests might need to seed data through Check .env files for test-specific envi

This is an excerpt. Refer to the complete source and its current requirements.