playwright-e2e-engineer

Create Playwright E2E tests with resilient selectors and CI evidence for critical user journeys.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill playwright-e2e-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-e2e-engineer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/playwright-e2e-engineer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill playwright-e2e-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create and harden Playwright end-to-end tests for business-critical browser journeys so real user flows keep working without flaky waits, brittle selectors, or bloated UI crawling.

Core Features & Use Cases

  • Critical journey coverage: Focuses on small, high-value specs for flows like signup, login, checkout, and core workflows.
  • Resilient test design: Uses user-facing locators, web-first assertions, deterministic test data, and storage-state-based auth setup.
  • CI-ready evidence: Wires traces, screenshots, videos, and honest run reporting so failures are diagnosable and pass-on-retry results are visible.
  • Use case: Use this Skill when you need to turn a fragile Playwright suite into a stable regression layer for the most important browser paths.

Quick Start

Ask for a Playwright E2E test plan or implementation for one critical user journey, including deterministic setup, resilient locators, and failure artifacts.

Frequently Asked Questions about playwright-e2e-engineer

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

FAQPage Schema
How do I fix flaky Playwright E2E tests in my CI pipeline?

Flaky Playwright E2E tests are fixed by replacing fixed waits with web-first assertions, using user-facing locators, and setting up deterministic test data. This Skill hardens existing suites by applying resilient test design and wiring failure artifacts like traces and screenshots for honest run reporting.

What's the best way to handle authentication state in Playwright browser testing?

Authentication state in Playwright browser testing is best handled using storage-state-based auth setup. This Skill implements auth-state reuse so repeated logins are eliminated, keeping critical journey specs like signup and checkout stable and fast across CI runs.

How do I set up Playwright E2E tests for critical user journeys like checkout?

Playwright E2E tests for critical user journeys like checkout are set up by focusing on small, high-value specs with deterministic setup and user-facing locators. This Skill implements resilient test designs covering core workflows in real browsers with CI-ready evidence.

Why does my Playwright test suite pass locally but fail in CI?

Playwright test suites pass locally but fail in CI due to non-deterministic data, brittle selectors, and missing web-first assertions. This Skill resolves these issues by enforcing deterministic test data, resilient locators, and honest run reporting with traces and screenshots.

Do I need to rewrite my entire UI test suite to stop flaky E2E tests?

You do not need to rewrite your entire UI test suite to stop flaky E2E tests. This Skill focuses on small, high-value critical journey specs like login and checkout, hardening existing suites against flakiness without bloated UI crawling.

Can I use Playwright for test automation without brittle CSS selectors?

Playwright for test automation can be used without brittle CSS selectors by relying on user-facing locators and web-first assertions. This Skill implements resilient test design to ensure critical browser user flows keep working without fragile selector dependencies.