playwright-pom
This Claude Code skill provides two guides for implementing Page Object Model patterns in Playwright test suites. It covers how to structure page objects for maintainability and includes a decision framework for choosing between POM, fixtures, and helpers based on test complexity and organizational needs.
git clone --depth 1 https://github.com/testdino-hq/playwright-skill /tmp/playwright-pom && cp -r /tmp/playwright-pom/pom ~/.claude/skills/playwright-pomSKILL.md
# Playwright Page Object Model > Structure your test code for maintainability — know when POM helps and when simpler patterns win. **2 guides** covering Page Object Model implementation and the decision framework for choosing between POM, fixtures, and helpers. ## Guide Index | Topic | Guide | |---|---| | Page Object Model patterns | [page-object-model.md](page-object-model.md) | | POM vs fixtures vs helpers | [pom-vs-fixtures-vs-helpers.md](pom-vs-fixtures-vs-helpers.md) |
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or have explicit authorization to test.