agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/playwright/SKILL.md

playwright

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the task needs real browser automation from the terminal for navigation, form filling, snapshots, screenshots, extraction, or UI-flow debugging; prefer the bundled `scripts/playwright_cli.sh` wrapper over ad-hoc browser code.

94 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use msw, react-hook-form and 8 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.
  • 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

  • MicrosoftSkill

    typescript

    TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.

    Also in 7 projects that use this

  • +1 more from thongdn-it

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 81 edited versions we read keep these.

  • 4

    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 for browser automation, UI flow debugging, reproducible interaction sequences, screenshots, and extraction tasks that need a real page …

    line 9
  2. Distinctive:

    Prefer explicit CLI actions through the wrapper script instead of jumping straight to custom code.

    line 15
  3. Distinctive:

    Do not reference stale element ids without taking a fresh snapshot.

    line 26
  4. Distinctive:

    Do not pivot to writing full Playwright test suites unless the user explicitly asks for test files.

    line 27

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

Intent

  • Use for browser automation, UI flow debugging, reproducible interaction sequences, screenshots, and extraction tasks that need a real page state.

Default operating pattern

  1. Confirm npx is available before relying on the wrapper script.
  2. Open the target page first, then snapshot before interacting so element references stay grounded in the current DOM.
  3. Re-snapshot after navigation or major UI changes; treat stale refs as a sign to refresh context instead of guessing.
  4. Prefer explicit CLI actions through the wrapper script instead of jumping straight to custom code.
  5. Capture screenshots or other artifacts whenever the user needs evidence, not just a verbal summary.

Bundled helper

  • scripts/playwright_cli.sh wraps @playwright/cli so the workflow can run without a global install.

Pack fit

  • Included in: automation-and-testing
  • Best for repeatable browser-driven QA, debugging, and data extraction loops.

Boundary

  • Do not reference stale element ids without taking a fresh snapshot.
  • Do not pivot to writing full Playwright test suites unless the user explicitly asks for test files.

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