← ClaudeAtlas

playwrightlisted

Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing, visual regression, API testing, component testing in TypeScript/JavaScript and Python projects.
secondsky/claude-skills · ★ 248 · Testing & QA · score 90
Install: claude install-skill secondsky/claude-skills
# Playwright - Browser Automation & E2E Testing Expert knowledge for browser automation and end-to-end testing with Playwright - a modern cross-browser testing framework. **IMPORTANT - Path Resolution:** This skill can be installed in different locations. Before executing commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands. Replace `$SKILL_DIR` with the actual discovered path. Common installation paths: - Plugin system: `~/.claude/plugins/*/playwright/skills/playwright` - Manual global: `~/.claude/skills/playwright` - Project-specific: `<project>/.claude/skills/playwright` ## CRITICAL WORKFLOW - Follow These Steps When automating browser tasks: 1. **Auto-detect dev servers** - For localhost testing, ALWAYS run server detection FIRST: ```bash cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(servers => console.log(JSON.stringify(servers)))" ``` - If **1 server found**: Use it automatically, inform user - If **multiple servers found**: Ask user which one to test - If **no servers found**: Ask for URL or offer to help start dev server 2. **Write scripts to /tmp** - NEVER write test files to skill directory; always use `/tmp/playwright-test-*.js` 3. **Use visible browser by default** - Always use `headless: false` unless user specifically requests headless mode 4. **Parameterize URLs** - Always make URLs configurable via constant at top of script 5. **Execute v