PL

playwright

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.zip

Installs 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 accessibility
70 charsno explicit “when” trigger
Intermediate

Key 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

You give it
User journey description or application feature
You get back
Playwright end-to-end test suite

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:

  1. page.getByRole() — semantic role + accessible name
  2. page.getByLabel() — form controls by label
  3. page.getByText() — visible text content
  4. page.getByPlaceholder() — input placeholders
  5. page.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.

SkillInstallsUpdatedSafetyDifficulty
playwright (this skill)01moReviewIntermediate
web-testing16moReviewIntermediate
dependency-upgrade265moReviewIntermediate
vitest416moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry