agentleFS
Sign inStart free
fmindfmind/dotfiles/skills/playwright/SKILL.md

playwright

Skill13 starsChanged 4 days agoMITView on GitHub

Automate browsers and E2E tests with Playwright: screenshots and traces.

94 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • hebertzhuSkill

    develop-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-itSkill

    msw

    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

  • SupabaseSkill

    react-hook-form

    Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,

    Also in 3 projects that use this

  • thongdn-itSkill

    tailwind

    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

  • VercelSkill

    react

    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

  • OpenAISkill

    web-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

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Playwright for browser automation and end-to-end tests.

    line 15
  2. Distinctive:

    Gather HTTP evidence before a browser: check status, headers, and bodies with xh.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 80 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Playwright

Use Playwright for browser automation and end-to-end tests. This skill owns the tool: browsers, commands, and the official skills; python-testing owns test design and fixtures.

Workflow

  1. Gather HTTP evidence before a browser: check status, headers, and bodies with xh; use a browser only for rendering, interaction, session state, or accessibility, driving it through roles and labels and checking state after every action.
  2. Pin the Python integration: uv add --dev playwright pytest-playwright, then uv run playwright install chromium; keep both packages in uv.lock. If Linux system libraries are missing, report the administrator-owned prerequisite instead of invoking the privileged install-deps command.
  3. Explore and record: uv run playwright codegen --target python-pytest <url> records a pytest test while a human drives the headed browser; uv run playwright screenshot <url> <file> (add --viewport-size=390,844 or --full-page as needed) and uv run playwright pdf <url> <file> produce review evidence. For a one-off render check outside a project that locks Playwright, run the same commands through uvx --from playwright==<version> playwright, installing chromium first; never add Playwright to an unrelated project.
  4. Run tests: uv run pytest -q tests/e2e --browser chromium --tracing retain-on-failure --screenshot only-on-failure. Inspect a saved trace from the shell with uv run playwright trace open <trace.zip> and the subcommands in uv run playwright trace --help (errors, actions, requests, console); trace close removes the extracted data. show-trace opens the GUI viewer for humans. To debug a failing test live, run it alone in the background with --playwright-debug=cli -s; when it pauses, attach with uv run playwright cli attach <session> from the printed instructions, then stop the background run and delete the .playwright-cli/ snapshot directory the CLI writes in the working directory.

Gotchas

  • Act only within authorized scope: use the profiles, accounts, data, and actions authorized for the task; reuse existing authorization. A test request alone does not authorize private browser-session reuse, cookie transfers, account creation, legal acceptance, purchases, paid browser services, real staging or production targets, destructive fixtures, or customer data; tear down only what the test created. When a required action falls outside that scope, prepare the local test and explain the specific missing authorization before proceeding. Treat login, MFA, and CAPTCHA as explicit authentication boundaries, never bypasses.
  • Reuse the shared browser cache: install only required browsers and reuse the default shared cache (~/.cache/ms-playwright on Linux). Do not run playwright uninstall as task teardown: other projects can need those binaries. Remove task-created temporary profiles and passing-run artifacts, preserve requested evidence and failure traces, and review native browser cleanup separately when disk pressure requires it.
  • Reinstall browsers after upgrades: browsers match the Playwright version that installed them; rerun uv run playwright install chromium after an upgrade.

Official Skills

Upstream: microsoft/playwright-cli provides the official browser CLI skill. Select it through the shared vendor-skill policy only for CLI-driven exploration; its commands are not the Python API. Python tests continue to use the documentation below and the project's uv lockfile. openai/skills also curates a same-name playwright skill that drives playwright-cli: preview it, never install it under that name (policy). The uv-locked package also ships version-matched playwright-cli, playwright-trace, and JavaScript-only playwright-component-testing skills in one directory; uv run playwright cli --help prints the playwright-cli path. Review each under the same policy before exposing it, including through uv run playwright trace install-skill, and check its allowed-tools: copies before Playwright 1.64 and playwright-cli 0.1.22 pre-approve all of npx (playwright-cli also npm); later ones narrow them to npx playwright.

Documentation

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free