playwright-skill
Skill0 starsChanged 3 months agoUnlicenseView on GitHub
Rules for running Playwright and Chrome/Chromium on macOS without touching the user's own Chrome. Use when the user mentions Playwright, playwrite, browser automation, UI tests, screenshots, Chrome or Chromium automation, headless browser, or the Playwright MCP.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- alibaklaea/claude-skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- testdino-hq/playwright-skilltheir own version, first seen Nov 13, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- zebbern/claude-code-guidetheir own version, first seen Oct 30, 2026
Used with
Projects with it also use playwright-ci, playwright-migration 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.
jovd83Skillplaywright-ci
CI and delivery skill for Playwright automation. Use when the agent needs to design, debug, or optimize Playwright execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.
Also in 3 projects that use this
jovd83Skillplaywright-migration
Migration skill for moving existing UI automation to Playwright. Use when the agent needs to translate Cypress or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
Also in 3 projects that use this
noahsilve123Skillpytest-skill
Generates production-grade pytest tests in Python with fixtures, parametrize, markers, mocking, and conftest patterns. Use when user mentions "pytest", "conftest", "@pytest.fixture", "@pytest.mark", "Python test". Triggers on: "pytest", "conftest", "Python test", "parametrize", "Python unit test".
Also in 3 projects that use this
noahsilve123Skillvitest-skill
Generates Vitest tests in JavaScript/TypeScript with Vite-native speed. Jest-compatible API with ESM support and HMR. Use when user mentions "Vitest", "vi.mock", "vitest.config". Triggers on: "Vitest", "vi.mock", "vi.fn", "Vite test", "vitest config".
Also in 3 projects that use this
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 5 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 5 projects that use this
- +1 more from jovd83
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- zebbern/claude-code-guide★ 4.7ksame name
- mercurjs/mercur★ 1.9ksame name
- testdino-hq/playwright-skill★ 419same name
- LambdaTest/agent-skills★ 391same name
- appautomaton/webmaton★ 20same name
- DangQuangSE/team-development-skills★ 19same name
- idanbeck/claude-skills★ 14same name
- xfstudio/skills★ 9same name
- TheArchitectit/awesome-cline-skills★ 8same name
- tstapler/dotfiles★ 8same name
22 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 repository17 other files it gives its agents.
- claude-agents-md/AGENTS.mdAGENTS.md
- claude-agents-md/CLAUDE.mdCLAUDE.md
- bash-skillSkill
- bug-recordingSkill
- bundle-sizeSkill
- changelog-skillSkill
- container-skillSkill
- fact-checkerSkill
- git-gh-skillSkill
- html-researchSkill
- index-html-skillSkill
- macos-electron-appsSkill
- pr-splitterSkill
- readme-skillSkill
- rerenderSkill
- scripts-skillSkill
- stacks-skillSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 5 are distinctive, and 13 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 8
Always run the browser headless.
- Distinctive: line 9
Never open a visible browser window unless the user explicitly asks to see it.
- Very specific: line 13
Only use the browser Playwright installs: npx playwright install chromium.
- Very specific: line 14
Never use channel: 'chrome', channel: 'msedge', --browser chrome or executablePath pointing at /Applications/Google Chrome.app.
- Very specific: line 15
Never use the user profile ~/Library/Application Support/Google/Chrome as userDataDir, not even a copy of it.
- Very specific: line 16
When a persistent context is needed, use a fresh temp dir: chromium.launchPersistentContext(fs.mkdtempSync(path.join(os.tmpdir(), 'pw-')), …
- Very specific: line 17
Never connectOverCDP to the user Chrome and never start the user Chrome with --remote-debugging-port.
- Very specific: line 18
Never pkill, killall or osascript quit Google Chrome.
- Distinctive: line 19
Never read or write the user Chrome cookies, history, bookmarks, passwords or extensions.
- Distinctive: line 23
Never edit the Info.plist or re-sign the Playwright Chromium app to hide it from the Dock, it stops launching.
- Very specific: line 24
When the user wants to see what happened, stay headless and give them a video (recordVideo), a trace (npx playwright show-trace) or …
- Distinctive: line 25
Only go headed when the user explicitly asks for it after knowing it will show in the Dock, and close the browser as soon as the task is …
- Very specific: line 29
Always pass --browser chromium.
- Very specific: line 30
Never --browser chrome, never --user-data-dir pointing at the user Chrome, never --extension.
- Very specific: line 31
When the MCP says the browser is not installed, install Chromium for the Playwright version the MCP uses.
- Very specific: line 35
Always close every browser, context and page, also when the script fails: use try / finally.
- Distinctive: line 36
Delete the temp profile dirs that were created.
- Very specific: line 37
Before finishing, check nothing is left: pgrep -fl ms-playwright must print nothing.
“Common” is measured: kept by at least 6 in 10 of the 29 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
Always Hidden
- Always run the browser headless.
headless: truein code,--headlessfor the Playwright MCP, never--headed. - Never open a visible browser window unless the user explicitly asks to see it.
- Screenshots, videos, traces and PDFs work headless. Never go headed to take them.
Never Touch The User Chrome
- Only use the browser Playwright installs:
npx playwright install chromium. It lives in~/Library/Caches/ms-playwright. - Never use
channel: 'chrome',channel: 'msedge',--browser chromeorexecutablePathpointing at/Applications/Google Chrome.app. - Never use the user profile
~/Library/Application Support/Google/ChromeasuserDataDir, not even a copy of it. - When a persistent context is needed, use a fresh temp dir:
chromium.launchPersistentContext(fs.mkdtempSync(path.join(os.tmpdir(), 'pw-')), { headless: true }). - Never
connectOverCDPto the user Chrome and never start the user Chrome with--remote-debugging-port. - Never
pkill,killallorosascript quitGoogle Chrome. Only close what was launched:await browser.close(). - Never read or write the user Chrome cookies, history, bookmarks, passwords or extensions.
When It Must Be Visible
- Headless is the only mode that keeps the browser out of the macOS Dock and the CMD + Tab switcher. A visible browser always shows in the Dock.
- Never edit the Info.plist or re-sign the Playwright Chromium app to hide it from the Dock, it stops launching.
- When the user wants to see what happened, stay headless and give them a video (
recordVideo), a trace (npx playwright show-trace) or screenshots instead. - Only go headed when the user explicitly asks for it after knowing it will show in the Dock, and close the browser as soon as the task is done.
Playwright MCP
- Configure it hidden and isolated:
npx @playwright/mcp@latest --headless --isolated --browser chromium. - Always pass
--browser chromium. It uses the Playwright Chrome for Testing, not/Applications/Google Chrome.app. - Never
--browser chrome, never--user-data-dirpointing at the user Chrome, never--extension. - When the MCP says the browser is not installed, install Chromium for the Playwright version the MCP uses. Never switch to
--browser chrometo work around it. - The MCP blocks
data:URLs, use a realhttporhttpsURL.
Cleanup
- Always close every browser, context and page, also when the script fails: use
try / finally. - Delete the temp profile dirs that were created.
- Before finishing, check nothing is left:
pgrep -fl ms-playwrightmust print nothing.
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.

