OpenSkillIndex← back to search
claude-code

Awesome-omni-skill playwright

Playwright E2E testing patterns and best practices. Cross-browser automation, selectors, fixtures, and CI integration. Trigger: When writing or running end-to-end tests with Playwright.

install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/testing-security/playwright-majiayu000" ~/.claude/skills/diegosouzapw-awesome-omni-skill-playwright && rm -rf "$T"
manifest: skills/testing-security/playwright-majiayu000/SKILL.md
source content

Playwright Skill

When to Use

  • End-to-end browser testing
  • Cross-browser automation
  • CI/CD integration

Critical Patterns

  • Use fixtures for setup
  • Prefer role-based selectors
  • Parallelize tests for speed

Decision Tree

  • UI or API E2E? → Use browser/page or request
  • Need screenshots? → Use page.screenshot
  • CI integration? → Use playwright/test

Edge Cases

  • Flaky network tests
  • Browser compatibility
  • Headless vs headed mode