Agent skill · software engineering · davila7
playwright-e2e-builder
Plan and build comprehensive Playwright E2E test suites with Page Object Model, authentication state persistence, custom fixtures, visual regression, and CI integration. Uses interview-driven planning to clarify critical user flows, auth strategy, test data approach, and parallelization before writing any tests.
Why this skill is useful
Adds specific Playwright test suite setup procedures and CI integration patterns that the AI wouldn't reliably generate on its own.
What it needs
Requires playwright installed locally. About 9k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Playwright E2E Test Suite Builder When to use 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 Phase 1: Explore (Plan Mode) Enter plan mode. Before writing any tests, explore the existing project: Project structure 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.) Application structure 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 environment variables CI/CD Check for existing CI config (.github/workflows/, .gitlab-ci.yml, Jenkinsfile) Look for Docker or docker-compose setup (useful for consistent test environments) Check if there's a staging/preview environment URL pattern Phase 2: Interview (AskUserQuestion) Use AskUserQuestion to clarify requirements. Ask in rounds. Round 1: Scope and critical flows Round 2: Authentication strategy for tests Round 3: Test data and environment Round 4: CI and parallelization Phase 3: Plan (ExitPlanMode) Write a concrete implementation plan covering: 1. Directory structure — test files, page objects, fixtures, config 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/playwright-e2e-builder