What problem does it solve?
Playwright users need a reliable way to convert existing Cypress or Selenium/WebDriver test suites without rewriting everything blindly.
Core Features & Use Cases
- Command and pattern mapping: translate common Cypress and Selenium idioms into Playwright equivalents, including navigation, locators, waits, assertions, and interactions.
- Architecture migration paths: adopt Playwright’s async/await flow, lazy locators, and built-in test runner concepts while changing how tests are structured.
- Incremental adoption strategy: move from framework-specific helpers (custom commands/page objects and WebDriver waits) to Playwright fixtures and assertions with fewer flake-prone waits.
Use Case: you want to migrate a flaky Cypress suite to Playwright while preserving intent by converting selectors, assertions, intercept/wait patterns, and test setup/teardown into Playwright-native patterns.
Quick Start
Ask the playwright-migration skill to generate a Cypress-to-Playwright conversion plan using the command mapping and mindset shifts described for reliability.