Skip to content
Skills Library
Programming · Testing

playwright-e2e

/playwright-e2e

Create, debug, or improve Playwright browser tests for user-visible workflows. Use when verifying navigation, form behavior, accessibility states, persistence, or cross-browser regressions.

Repository
skillsmo ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create, debug, or improve Playwright browser tests for user-visible workflows. Use when verifying navigation, form behavior, accessibility states, persistence, or cross-browser regressions.

Original author description

Create, debug, or improve Playwright browser tests for user-visible workflows. Use when verifying navigation, form behavior, accessibility states, persistence, or cross-browser regressions.

How it works

  1. Goal
  2. Workflow
  3. Decision rules
  4. Boundaries
  5. Completion standard
  6. Further reading
Original SKILL.md headings · 35 lines, 249 words
SKILL.md preview
---
name: playwright-e2e
description: "Create, debug, or improve Playwright browser tests for user-visible workflows. Use when verifying navigation, form behavior, accessibility states, persistence, or cross-browser regressions."
---

# Playwright end-to-end testing

## Goal

Cover critical user journeys with stable assertions that match observable behavior.

## Workflow

1. Inspect app start commands, test configuration, fixtures, browser matrix, authentication strategy, and existing selectors.
2. Choose a user journey and define its observable initial state, action, result, and failure/recovery state.
3. Use accessible roles and labels where practical; isolate data, control network dependencies, and wait on meaningful conditions.
4. Assert user-visible outcomes and relevant URL or persisted state without relying on incidental implementation details.
5. Run the focused test and relevant suite; inspect traces, screenshots, or logs for failures and report browser coverage.

## Decision rules

- Use API setup only to arrange state when the UI behavior under test remains exercised.
- Prefer deterministic fixtures and isolated accounts over shared mutable test data.
- Add a new browser or viewport when it protects a supported user environment.

## Boundaries

- Do not use arbitrary sleeps as synchronization.
- Do not make an end-to-end suite depend on live third-party systems unless that dependency is the explicit target.

## Completion standard

Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request.

## Further reading

- [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases.
- [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
  • SKILL.md 2 KB
  • references/field-guide.md 1 KB
  • references/source-notes.md 1 KB

Versions

RepositoryScoreLicence
This page · helx0071/skillsmo90MIT
5dive-ai/skills100MIT
market0v0/shipkit100MIT
hmislk/hmis98GPL-3.0
RobinBeraud/claude-qa-skills90MIT

Database snapshot: 13.11.2026 · package version a187ec8ae02f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100e2e-playwright-testing
    End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, form submission testing, or user flow testing. Triggers on "playwright", "e2e test", "browser test", "end-to-end", "form flow testing", or test files in tests/e2e/.
  • 95playwright-test
    Creates Playwright browser-based end-to-end tests for Next.js pages covering complete user journeys from start to finish. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing,…
  • 100setup-e2e-testing
    Set up Playwright + Testcontainers + axe-core for e2e and accessibility testing. Includes patterns for forms, tables, workflows. Use when setting up e2e tests or writing Playwright tests.
  • 100playwright
    Write, run, and maintain reliable end-to-end tests with Playwright. Use for test generation, CI integration, trace debugging, and cross-browser validation.
  • 100playwright-testing
    UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.
  • 95playwright-e2e-automation
    Master enterprise Playwright end-to-end (E2E) automation, Page Object Model (POM) architecture, cross-browser testing, network mocking, visual regression testing, and CI pipeline integrations. Trigger when writing Playwright tests, automating web UI E2E flows, or configuring…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.