playwright
Skill4 starsChanged 5 months agoApache-2.0View on GitHub
Browser automation and end-to-end testing with Playwright. Use when building/testing frontends, automating user workflows, taking screenshots, validating UI state, filling forms, testing across browsers, or mentions "playwright", "E2E test", "browser automation", "screenshot".
- Reads credentials
94 other projects use a version of this.
Adopted by
Most recently taken up by
- Pamir-AI/skillstheir own version, first seen Nov 8, 2026
- shetengteng/skillix-hubtheir own version, first seen Nov 8, 2026
- LuisSambrano/antigravity-configtheir own version, first seen Nov 8, 2026
- fmind/dottheir own version, first seen Nov 8, 2026
- fmind/dotfilestheir own version, first seen Nov 8, 2026
- miminashi/pvesetheir own version, first seen Nov 4, 2026
Used with
Projects with it also use develop-web-game, msw and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
hebertzhuSkilldevelop-web-game
Use when building or iterating on a web game and you need a tight implement-test-observe loop; prefer the bundled Playwright client, inspect screenshots and text state, and validate every meaningful change before moving on.
Also in 4 projects that use this
thongdn-itSkillmsw
MSW (Mock Service Worker) best practices for API mocking in tests (formerly test-msw). This skill should be used when setting up MSW, writing request handlers, or mocking HTTP APIs. This skill does NOT cover general testing patterns (use test-vitest or test-tdd skills) or test methodology.
Also in 3 projects that use this
SupabaseSkillreact-hook-form
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,
Also in 3 projects that use this
thongdn-itSkilltailwind
Tailwind CSS v4 performance optimization and best practices guidelines (formerly tailwindcss-v4-style). This skill should be used when writing, reviewing, or refactoring Tailwind CSS v4 code to ensure optimal build performance, minimal CSS output, and correct usage of v4 features. Triggers on tasks involving Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
Also in 5 projects that use this
VercelSkillreact
React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.
Also in 6 projects that use this
OpenAISkillweb-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (FCP, LCP, TBT, CLS, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
Also in 5 projects that use this
- +1 more from thongdn-it
Other versions94 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 94
- openai/openai-agents-python★ 31ksame name
- openai/skills★ 27ksame name
- prowler-cloud/prowler★ 15ksame name
- hyperdxio/hyperdx★ 10ksame name
- bluesky-social/atproto★ 9.7ksame name
- netease-youdao/LobsterAI★ 6.2ksame name
- Kiln-AI/Kiln★ 5.3ksame name
- freestylefly/wesight★ 969same name
- Gram-ax/gramax★ 609same name
- JetBrains/skills★ 386same name
84 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- api-designSkill
- improve-codebase-architectureSkill
- architectureSkill
- cicdSkill
- cloud-infraSkill
- codebase-navigatorSkill
- code-qualitySkill
- code-reviewSkill
- code-standardsSkill
- configuration-managementSkill
- contract-testingSkill
- dependency-managementSkill
- diagnoseSkill
- documentationSkill
- dynamic-routingSkill
- enterprise-architectureSkill
- enterprise-test-suitesSkill
- git-guardrails-claude-codeSkill
- grill-meSkill
- handoffSkill
- intent-clarificationSkill
- triageSkill
- legacy-modernizationSkill
- llm-evalsSkill
- observabilitySkill
- ops-sreSkill
- performance-optimizationSkill
- to-issuesSkill
- to-prdSkill
- setup-pre-commitSkill
- prototypeSkill
- pr-reviewSkill
- ralph-loopSkill
- requirementsSkill
- root-cause-analysisSkill
- security-auditSkill
- security-patchingSkill
- startup-lifecycleSkill
- tddSkill
- testingSkill
- threat-modelingSkill
- to-issuesSkill
- token-efficiencySkill
- to-prdSkill
- ux-designSkill
- write-a-skillSkill
- zoom-outSkill
The file
Files
Skill: Playwright Browser Automation
Browser automation, visual testing, and end-to-end test generation with Playwright. Launch browsers, navigate pages, interact with the DOM, capture screenshots, validate UI state, run multi-browser tests.
Use Cases
End-to-end testing — User flows from login → action → verification. Tests through public UI, not mocks.
Visual validation — Screenshots for design regression, visual diffs, accessibility checks.
Form automation — Fill complex forms, validate errors, test input constraints.
Cross-browser testing — Run same tests against Chromium, Firefox, Safari.
Prototype validation — Verify prototype UI behavior, click flows, state transitions.
Accessibility testing — Check ARIA labels, keyboard navigation, color contrast via Playwright + axe.
Patterns
1. Setup & Config
// playwright.config.js
import { defineConfig } from '@playwright/test';
export default defineConfig({
testDir: './e2e',
fullyParallel: true,
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 2 : 0,
workers: process.env.CI ? 1 : undefined,
use: {
baseURL: 'http://localhost:3000',
trace: 'on-first-retry',
screenshot: 'only-on-failure',
},
webServer: {
command: 'npm run dev',
url: 'http://localhost:3000',
reuseExistingServer: !process.env.CI,
},
projects: [
{ name: 'chromium', use: { ...devices['Desktop Chrome'] } },
{ name: 'firefox', use: { ...devices['Desktop Firefox'] } },
{ name: 'webkit', use: { ...devices['Desktop Safari'] } },
{ name: 'mobile', use: { ...devices['Pixel 5'] } },
],
});2. Page Object Model (DRY selectors)
// e2e/pages/login.page.ts
import { Page, Locator } from '@playwright/test';
export class LoginPage {
readonly page: Page;
readonly emailInput: Locator;
readonly passwordInput: Locator;
readonly submitButton: Locator;
readonly errorMessage: Locator;
constructor(page: Page) {
this.page = page;
this.emailInput = page.locator('input[type="email"]');
this.passwordInput = page.locator('input[type="password"]');
this.submitButton = page.locator('button[type="submit"]');
this.errorMessage = page.locator('[role="alert"]');
}
async goto() {
await this.page.goto('/login');
}
async login(email: string, password: string) {
await this.emailInput.fill(email);
await this.passwordInput.fill(password);
await this.submitButton.click();
}
}3. Test Structure (Given-When-Then)
// e2e/auth.spec.ts
import { test, expect } from '@playwright/test';
import { LoginPage } from './pages/login.page';
test.describe('Authentication', () => {
let loginPage: LoginPage;
test.beforeEach(async ({ page }) => {
loginPage = new LoginPage(page);
await loginPage.goto();
});
test('user can login with valid credentials', async ({ page }) => {
// Given: user is on login page (beforeEach)
// When: user enters credentials and submits
await loginPage.login('user@example.com', 'password123');
// Then: redirected to dashboard
await expect(page).toHaveURL('/dashboard');
});
test('user sees error on invalid credentials', async () => {
// When: user enters wrong password
await loginPage.login('user@example.com', 'wrong');
// Then: error message shown
await expect(loginPage.errorMessage).toBeVisible();
await expect(loginPage.errorMessage).toContainText('Invalid credentials');
});
});4. Visual Testing
test('dashboard layout matches snapshot', async ({ page }) => {
await page.goto('/dashboard');
// Screenshot for visual regression
await expect(page).toHaveScreenshot('dashboard.png');
});5. API Mocking (test offline flows)
test('shows error when API fails', async ({ page }) => {
// Mock API endpoint to simulate failure
await page.route('**/api/data', route => {
route.abort('failed');
});
await page.goto('/');
// Verify error UI shown
await expect(page.locator('[role="alert"]')).toContainText('Failed to load');
});Best Practices
Use Page Object Model — Centralize selectors, reduce duplication, make refactors trivial.
One assertion per test — Tests are faster, failures are clear, parallelization improves.
Use locators, not CSS strings — page.locator('button:has-text("Login")') is expressive, maintainable.
Wait for readiness, not time — page.waitForLoadState(), expect(locator).toBeVisible(), never sleep().
Test behavior, not implementation — Click buttons, fill forms, check what users see. Don't query internal state.
Mock external APIs — Tests run offline, fast, deterministic. Only test your code.
Run in CI with retries — Transient failures happen; retries catch flakes without making tests slower locally.
Commands
# Run all tests
npx playwright test
# Run single file
npx playwright test e2e/auth.spec.ts
# Run tests matching pattern
npx playwright test -g "login"
# Debug mode (opens inspector)
npx playwright test --debug
# UI mode (visual test runner)
npx playwright test --ui
# Generate test from recording
npx playwright codegen http://localhost:3000Integration with SDLC
Phase 2 (Design): Prototype validation — verify UI flows work as designed Phase 3 (Dev): Feature tests during implementation — TDD for E2E Phase 4 (Test): Full E2E test suite, visual regression, accessibility Phase 5 (Deploy): Pre-deployment smoke tests, cross-browser validation
Status: Ready for E2E test generation and browser automation
Best for: Frontend testing, design validation, cross-browser coverage, accessibility verification
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
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.

