playwright-testing
Skill1 starsChanged 5 months agoMITView on GitHub
Test web applications using Playwright — automate browser testing, verify UI functionality, capture screenshots for debugging
- Installs packages
18 other projects use a version of this.
Adopted by
Most recently taken up by
- n-n-code/n-n-code-skillstheir own version, first seen Nov 1, 2026
- suryas91/claude-skillstheir own version, first seen Oct 11, 2026
- TangleML/tangle-uitheir own version, first seen Oct 8, 2026
- PrairieLearn/PrairieLearntheir own version, first seen Oct 8, 2026
- fossasia/visdomtheir own version, first seen Oct 8, 2026
- alinaqi/claude-bootstraptheir own version, first seen Oct 8, 2026
Used with
Projects with it also use security.
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.
0xSeroSkillsecurity
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- fossasia/visdom★ 10ksame name
- podman-desktop/podman-desktop★ 8.1ksame name
- silvertakana/worldwideview★ 1.9ksame name
- marmelab/atomic-crm★ 1.4ksame name
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
- PrairieLearn/PrairieLearn★ 530same name
- Community-Access/accessibility-agents★ 409same name
- chongdashu/vibejam-starter-pack★ 147same name
- TangleML/tangle-ui★ 104same name
8 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 repository84 other files it gives its agents.
- api-design-reviewerSkill
- api-test-suite-builderSkill
- ask-mattSkill
- aws-solution-architectSkill
- captureSkill
- changelog-generatorSkill
- ci-cd-pipeline-builderSkill
- cloud-securitySkill
- codebase-designSkill
- codebase-onboardingSkill
- code-reviewerSkill
- context-compressSkill
- context-modeSkill
- database-designerSkill
- database-schema-designerSkill
- dependency-auditorSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- env-secrets-managerSkill
- finish-branchSkill
- firecrawlSkill
- focused-fixSkill
- frontend-designSkill
- get-shit-doneSkill
- git-guardrails-claude-codeSkill
- git-worktree-managerSkill
- git-worktreesSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- incident-commanderSkill
- incident-responseSkill
- mcp-builderSkill
- memSkill
- migration-architectSkill
- monorepo-navigatorSkill
- observability-designerSkill
- performance-profilerSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- prompt-engineeringSkill
- prototypeSkill
- pr-review-expertSkill
- rag-architectSkill
- red-teamSkill
- reflectSkill
- resolving-merge-conflictsSkill
- root-cause-tracingSkill
- runbook-generatorSkill
- self-evalSkill
- senior-architectSkill
- senior-backendSkill
- senior-devopsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
1
Distinctive
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
- Very specific: line 96
Use data-testid attributes for reliable selectors
- Distinctive: line 97
Avoid XPath — use Playwright's built-in locators
- Very specific: line 98
Use page.waitForLoadState() after navigation
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Playwright Testing
Automate browser-based testing for web applications.
When to Use
- Testing frontend functionality in real browser
- Verifying UI interactions (clicks, forms, navigation)
- Debugging visual issues
- Capturing screenshots for documentation
- Cross-browser compatibility testing
Setup
# Install Playwright
npm init playwright@latest
# Or add to existing project
npm install -D @playwright/testWriting Tests
Basic Test
import { test, expect } from '@playwright/test';
test('homepage loads correctly', async ({ page }) => {
await page.goto('http://localhost:3000');
await expect(page).toHaveTitle(/My App/);
await expect(page.locator('h1')).toContainText('Welcome');
});Form Interaction
test('login form submits', async ({ page }) => {
await page.goto('/login');
await page.fill('#email', 'user@example.com');
await page.fill('#password', 'password123');
await page.click('button[type="submit"]');
await expect(page).toHaveURL('/dashboard');
});Screenshot
test('capture screenshot', async ({ page }) => {
await page.goto('http://localhost:3000');
await page.screenshot({ path: 'screenshot.png', fullPage: true });
});API Mocking
test('handles API error', async ({ page }) => {
await page.route('**/api/data', route => {
route.fulfill({ status: 500, body: 'Server Error' });
});
await page.goto('/');
await expect(page.locator('.error')).toBeVisible();
});Running Tests
# Run all tests
npx playwright test
# Run specific file
npx playwright test tests/login.spec.ts
# Run in headed mode (see browser)
npx playwright test --headed
# Run with UI mode
npx playwright test --ui
# Generate report
npx playwright show-reportBest Practices
- Use
data-testidattributes for reliable selectors - Avoid XPath — use Playwright's built-in locators
- Use
page.waitForLoadState()after navigation - Mock API calls in unit tests, hit real APIs in E2E
- Take screenshots on failure for debugging
// Good: resilient selector
page.getByRole('button', { name: 'Submit' })
// Bad: fragile selector
page.locator('.css-x7y3k > div:nth-child(3) > button')Debugging
// Pause for inspection
await page.pause();
// Debug with console logs
page.on('console', msg => console.log(msg.text()));
// Trace for post-mortem analysis
npx playwright test --trace on
npx playwright show-trace trace.zipDoes 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.

