Automate user journey testing and accessibility checks using Playwright. Ensure cross-browser reliability without hard-coded waits.
Install
mkdir -p .claude/skills/playwright-lfr-ai && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14960" && unzip -o skill.zip -d .claude/skills/playwright-lfr-ai && rm skill.zipInstalls to .claude/skills/playwright-lfr-ai
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
End-to-end testing with Playwright for user journeys and accessibilityKey capabilities
- →Write end-to-end tests for user journeys
- →Verify accessibility compliance with semantic locators
- →Configure cross-browser testing
- →Set up test retries for CI stability
- →Capture screenshots on test failure
- →Use Playwright's auto-waiting mechanism
How it works
The skill generates Playwright tests that prioritize accessible locators to verify critical user journeys and accessibility. It incorporates best practices like retries and screenshot captures for stable CI/CD execution.
Inputs & outputs
When to use playwright
- →Create tests for critical user authentication flows
- →Verify component accessibility via semantic roles
- →Configure cross-browser testing for web applications
- →Implement automatic retries for CI test stability
About this skill
Playwright E2E Testing Skill
Purpose
Write and maintain end-to-end tests that verify critical user journeys, accessibility compliance, and cross-browser behavior using Playwright.
Locator Priority
Use accessible locators in this order:
page.getByRole()— semantic role + accessible namepage.getByLabel()— form controls by labelpage.getByText()— visible text contentpage.getByPlaceholder()— input placeholderspage.getByTestId()— last resort for complex selectors
Best Practices
- Test critical user journeys, not individual components.
- Configure retries for CI (
retries: 2). - Capture screenshots on failure.
- Never hard-code sleeps/timeouts; rely on Playwright auto-waiting.
- Run against production build when possible.
Running Tests
task test:e2e
task test:e2e:headed
task test:e2e:install
When not to use it
- →When testing individual components instead of user journeys
- →When hard-coding sleeps or timeouts in tests
- →When not running against a production build
Limitations
- →Tests should focus on critical user journeys
- →Requires configuration for CI retries and screenshot capture
- →Relies on Playwright's auto-waiting for stability
How it compares
This skill focuses on generating Playwright tests with semantic locators and built-in stability features, which is more reliable and maintainable than tests relying on fragile CSS selectors or manual waits.
Compared to similar skills
playwright side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| playwright (this skill) | 0 | 1mo | Review | Intermediate |
| web-testing | 1 | 7mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| vitest | 41 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
web-testing
mrgoonie
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
vitest
antfu
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
typescript-review
metabase
Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.
accessibility-compliance
wshobson
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
browser-tools
Whamp
Lightweight Chrome automation toolkit with shared configuration, JSON-first output, and six focused scripts for starting, navigating, inspecting, capturing, evaluating, and cleaning up browser sessions.