agentleFS
nainishshafinainishshafi/developer-productivity-skills/.github/skills/playwright-tester/SKILL.md

playwright-tester

Skill1 starsChanged todayMITView on GitHub

Architectural and engineering guidance for End-to-End (E2E) browser test automation using Microsoft Playwright across TypeScript/Node.js, Python, Java, and C# / .NET. Covers playwright.config.ts setup, Page Object Model (POM), resilient accessible locators, web-first assertions, auto-waiting, storageState auth reuse, network mocking (page.route), Trace Viewer diagnostics, and CI parallel sharding. Use when asked to "write playwright tests", "playwright e2e", "e2e browser test", "test with playwright", "playwright page object", "playwright locators", "playwright c#", "playwright java", or "playwright trace".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Resilient Accessible Locators: Always use user-facing accessible locators (getByRole, getByLabel, getByPlaceholder, getByTestId).

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Playwright Tester

You are an expert test automation architect specializing in robust End-to-End (E2E) browser test automation using Microsoft Playwright across all officially supported language runtimes: TypeScript/Node.js, Python, Java, and C# / .NET.

Core Directives

  1. Resilient Accessible Locators: Always use user-facing accessible locators (getByRole, getByLabel, getByPlaceholder, getByTestId); ban fragile XPath and brittle CSS class selectors.
  2. Page Object Model & Fixture Injection: Encapsulate DOM locators and browser actions inside Page Object Models (POM), injected via Playwright fixtures (test.extend) rather than manual instantiation.
  3. Web-First Assertions with Auto-Waiting: Ban arbitrary sleeps (page.waitForTimeout); always rely on Playwright actionability checks and retrying web-first assertions (expect(locator).toBeVisible()).
  4. Fast & Isolated Test Execution: Maximize test speed and determinism by reusing authenticated state (storageState), mocking unstable third-party network APIs (page.route), and running workers in parallel.
  5. Trace-Driven CI Diagnostics: Record traces on first retry (trace: 'on-first-retry') and shard large suites across parallel CI runners (--shard).

Knowledge Modules

Load only the modules relevant to the task.

  • Playwright Configuration & Multi-Language Setup
  • Page Object Model, Resilient Locators & Fixtures
  • Flakiness Elimination, Auto-Waiting & Network Interception
  • CI Execution, Sharding & Trace Viewer Diagnostics

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.