playwright-skill

Write Playwright end-to-end, API, component, visual, accessibility, and security tests.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/swongsuddee/windflu-test --skill playwright-skill-swongsuddee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/swongsuddee/windflu-test/tree/main/.agents/toolkit/playwright-skill
Command: npx skills add https://github.com/swongsuddee/windflu-test --skill playwright-skill-swongsuddee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork from writing and debugging Playwright tests by providing proven patterns for stable locators, assertions, fixtures, auth, and CI execution.

Core Features & Use Cases

  • Battle-tested Playwright patterns: Use web-first assertions, resilient selector strategies, and reliable waiting rules to reduce flakiness.
  • E2E and API coverage: Guide end-to-end flows and API testing with request context patterns and response validation.
  • Scalable test operations: Apply auth storage state reuse, Playwright CI practices, tracing workflows, and reporting strategies.
  • Quality gates: Integrate accessibility, visual regression, and security-oriented testing approaches for owned applications.

Quick Start

Ask the agent: "Show me how to design a stable authenticated Playwright test with role-based locators, storageState reuse, and trace-on-first-retry debugging for a flaky UI page."

Frequently Asked Questions about playwright-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write stable Playwright tests that don't flake?

Stable Playwright tests use web-first assertions and resilient selector strategies to reduce flakiness. This approach eliminates manual waiting by automatically retrying assertions until conditions pass, ensuring reliable end-to-end execution.

What is the best way to reuse authentication state in Playwright across multiple tests?

Playwright reuses authentication state by implementing storageState configurations. This method saves and injects browser context storage, allowing subsequent tests to bypass login flows and execute authenticated scenarios faster.

Can I run accessibility and visual regression tests using Playwright?

Playwright supports integrating accessibility and visual regression testing approaches for owned applications. These quality gates validate UI compliance and visual consistency directly within your end-to-end test suite execution.

How do I debug a flaky Playwright UI test using tracing?

Debug flaky Playwright UI tests by enabling trace-on-first-retry configurations. Tracing captures screenshots, DOM snapshots, and network events during execution, providing detailed logs to isolate timing or selector failures.

Does Playwright support sharding and CI-ready reporting for large test suites?

Playwright supports CI-ready reporting and sharding to scale large test suites. Sharding splits test execution across multiple machines, while built-in reporters generate consistent results for continuous integration pipelines.

When do I need to establish safety trust boundaries for Playwright agent workflows?

Safety trust boundaries are required for Playwright agent workflows when targeting owned or authorized applications. Establishing these boundaries ensures deterministic automated execution without unintended external system interactions.