1. Habit
  2. Skills
  3. Playwright Automation skill
petrkindlmann · 2K installs

Playwright Automation skill
Runs by itself, PR changes e2e tests.

E2E tests that stay stable.

Install the Playwright Automation skill and make it a habit: follow https://gethabit.dev/skills/petrkindlmann/playwright-automation.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

2K installs203 starsMIT licenceSource on GitHub ↗

Playwright Automation

by petrkindlmann · 2K installs

The skill

Playwright automation is a skill for QA and frontend engineers who write production-grade Playwright tests in TypeScript with page objects, fixtures, user-facing locators, parallel runs, CI sharding and version checks.

Only when you ask.

The habit

E2E tests that stay stable.

↻ Runs by itselfPR changes e2e tests

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

PR changes e2e tests. Runs in GitHub Actions or Claude Code routine.

  • ↻ PR changes e2e tests
  • pull_request.opened touching e2e/

02

It checks its work

list, grep and tsc. If a check fails, it tries again.

  • ✓npx playwright test --list discovers the tests
  • ✓grep -rn 'waitForTimeout\|page.pause' e2e/ prints nothing
  • ✓npx tsc --noEmit passes
  • ✓playwright.config.ts sets forbidOnly for CI

03

It remembers

QA project context. The next run reads it first: language, browsers, team maturity and known gaps.

.agents/qa-project-context.md

One run, step by step.
Then it stops.

Stop ruleStops after one pull request per run, with two retries.

  1. 01

    Read context

    Read .agents/qa-project-context.md and ask the user only what it does not answer.

  2. 02

    Check versions

    Run npm ls @playwright/test playwright and npx playwright --version before version-sensitive APIs.

  3. 03

    Check locators

    Prefer getByRole, getByLabel and getByTestId over CSS or xpath.

  4. 04

    Check structure

    Confirm fixtures for setup, page objects without expect and isolated test data.

  5. 05

    Run the gates

    Run --list, the waitForTimeout grep and tsc --noEmit.

  6. 06

    Route special cases

    Send flaky fixes to test-reliability and visual baselines to visual-testing.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Playwright Automation skill helps.

Use it when

  • ✓ You start a Playwright suite
  • ✓ You write page objects
  • ✓ You set up sharding in CI

Skip it when

  • – You fix one flaky test
  • – You need deep WCAG audits

Questions

Playwright Automation skill, answered.

Why ban waitForTimeout?

The skill says actions and web-first assertions already auto-wait, so timeouts hide the real condition.

Can lint enforce this?

Yes. The skill names eslint-plugin-playwright rules such as no-wait-for-timeout.

How do I install the Playwright Automation skill?

Copy the prompt at the top into your agent. It installs the skill from petrkindlmann/qa-skills and sets up the habit. Or run npx skills add petrkindlmann/qa-skills --skill playwright-automation.

Is the Playwright Automation skill free?

Yes. It is published under MIT. Habit is free too.

Playwright Automation. Now as a habit.

Install the Playwright Automation skill and make it a habit: follow https://gethabit.dev/skills/petrkindlmann/playwright-automation.md

  • Free
  • No account
  • Undo in one line

All petrkindlmann skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by petrkindlmann, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.