What problem does it solve?
This skill should be used when writing, refactoring, or modifying Playwright E2E test code. It covers creating test files from TC-ID specs, converting browser exploration results to executable tests, refactoring locators or fixtures, adding API mocking, test data setup/teardown, and parallel-safe isolation. Includes locator strategy hierarchy, auth setup patterns, fixture design, teardown strategies, and network interception recipes. Triggers: "write a test for", "add a test case", "refactor this locator", "add error path tests", "convert specs to code", "add API mocking", "set up auth for tests". NOT for: full pipeline from scratch (use add-playwright-tests), shared live-site exploration (use capture-feature-evidence), generating specs without code (use plan-test-coverage or generate-test-cases), diagnosing flaky tests (use fix-flaky-tests).
Core Features & Use Cases
- Create test files from TC-ID specs and browser exploration results
- Refactor locators, fixtures, and page objects for stability and maintainability
- Add API mocking, test data setup/teardown, and parallel-safe isolation
- Include locator strategy hierarchy, auth setup patterns, fixtures, teardown, and network interception recipes
Quick Start
Provide a TC-ID spec or exploration result and the skill will generate a Playwright test file with fixtures and page objects.