playwright-authAuthenticate Playwright tests once and reuse the session — setup projects, storageState, per-role and per-worker auth, API login, and handling MFA/SSO. Use when tests need a logged-in user, when login is repeated in beforeEach, or when auth state leaks between tests.
playwright-ciRun Playwright in CI — GitHub Actions and other providers, sharding, reporters, artifact upload, Docker, and keeping suites fast and non-flaky on shared runners. Use when adding e2e to a pipeline, splitting a slow suite, or triaging CI-only failures.
playwright-debugDiagnose failing or flaky Playwright tests — trace viewer, UI mode, headed/debug runs, timeout triage, strict-mode violations, and flakiness root causes. Use when a test fails, passes locally but fails in CI, or fails intermittently.
playwright-exploreDrive a real browser through the Playwright MCP server to test a website by hand the way a user would — navigate, fill forms with realistic data, submit, and verify what actually happened. Use for exploratory testing, reproducing a reported bug, checking a flow before automating it, or turning a man
playwright-ralph-loopRun an agent in a Ralph loop against a Playwright suite — repeatedly re-running one prompt in a fresh context to drive a red suite green, or to build out coverage one flow per iteration. Use when asked to "loop until tests pass", "keep fixing until green", autonomously grow e2e coverage, or set up a
playwright-setupScaffold or repair a Playwright test project — install, playwright.config.ts, directory layout, webServer, projects/devices, baseURL. Use when a repo has no Playwright yet, when adding a browser/mobile project, or when `npx playwright test` fails to start (config, browsers-not-installed, server-not-
playwright-write-testAuthor Playwright e2e tests — locator choice, web-first assertions, test structure, page objects, custom fixtures, network mocking. Use whenever writing a new .spec.ts, converting a manual test case to automation, or reviewing test code for resilience.