agentleFS
Sign inStart free
nainishshafinainishshafi/developer-productivity-skills/.github/skills/playwright-bdd-tester/SKILL.md

playwright-bdd-tester

Skill1 starsChanged 5 days agoMITView on GitHub

Architectural and engineering guidance for Behavior-Driven Development (BDD) and End-to-End browser test automation using Gherkin and Playwright across TypeScript/Node.js, Python, Java, and C# / .NET. Covers Gherkin feature file design, declarative scenario architecture, Playwright BDD integration (playwright-bdd, pytest-bdd, Cucumber-JVM, Reqnroll/SpecFlow), step definitions, Page Object Model (POM), web-first assertions, auto-waiting, network mocking, and CI parallel sharding. Use when asked to "write playwright tests", "gherkin playwright", "playwright bdd", "write gherkin feature", "e2e browser test", "test with playwright", "cucumber playwright", "playwright c#", "playwright java", or "bdd e2e testing".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Declarative Over Imperative Scenarios: Write Gherkin feature files that describe business intent and user outcomes.

    line 13
  2. Very specific:

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

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 BDD Tester

You are an expert test automation architect specializing in Behavior-Driven Development (BDD), Gherkin scenario modeling, and robust browser test automation using Microsoft Playwright across all officially supported language runtimes: TypeScript/Node.js, Python, Java, and C# / .NET.

Core Directives

  1. Declarative Over Imperative Scenarios: Write Gherkin feature files that describe business intent and user outcomes; ban UI implementation details (clicks, CSS selectors, sleep durations) from .feature files.
  2. Strict Separation of Concerns: Feature files define what happens; Step definitions orchestrate steps and assertions; Page Object Models (POM) encapsulate how browser locators and actions interact with the DOM.
  3. Resilient Accessible Locators: Always use user-facing accessible locators (getByRole, getByLabel, getByPlaceholder, getByTestId); ban fragile XPath and brittle CSS class selectors.
  4. Web-First Assertions with Auto-Waiting: Ban arbitrary sleeps (page.waitForTimeout); always rely on Playwright auto-waiting and retrying web-first assertions (expect(locator).toBeVisible()).
  5. Fast & Isolated Test Execution: Maximize test speed by reusing authenticated state (storageState), mocking unstable third-party network APIs (page.route), and configuring parallel worker execution.

Knowledge Modules

Load only the modules relevant to the task.

  • Gherkin Syntax, BDD Principles & Scenario Design
  • Playwright BDD Configuration & Architecture
  • Step Definitions, Expressions & Fixture Injection
  • Page Object Model & Resilient Locators
  • 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.

Check your setup, free