agentleFS
Sign inStart free
kiku-jwkiku-jw/codex-skills/playwright/SKILL.md

playwright

Skill0 starsChanged 4 months agoMITView on GitHub

Drive a real browser from the terminal with the bundled Playwright CLI wrapper. Use when the task requires navigation, form filling, snapshots, screenshots, data extraction, or UI-flow debugging without turning the job into a Playwright test suite.

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

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

  • 0

    Common

    Most of the 81 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use when: the task is to author Playwright test files or when a different built-in browser tool already solves the job better.

    line 10
  2. Very specific:

    Check prerequisites first: command -v npx >/dev/null 2>&1.

    line 17
  3. Distinctive:

    Run the core loop through the wrapper: open the page, snapshot, interact using refs from the latest snapshot, and snapshot again after …

    line 18
  4. Very specific:

    Always snapshot before using element refs like e12.

    line 22
  5. Very specific:

    Prefer explicit CLI commands over eval/custom code when the wrapper can already do the job.

    line 24
  6. Very specific:

    Use --headed when a visual check materially helps.

    line 25

“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 CLI Skill

Metadata

  • Trigger when: the user needs browser automation or browser-state inspection from the terminal.
  • Do not use when: the task is to author Playwright test files or when a different built-in browser tool already solves the job better.

Skill Purpose

Provide a deterministic CLI-first browser workflow that always starts from a fresh snapshot and uses stable element refs instead of ad hoc DOM poking.

Instructions

  1. Check prerequisites first: command -v npx >/dev/null 2>&1. If npx is missing, stop and ask the user to install Node/npm. Otherwise use the exact wrapper script at ~/.codex/skills/playwright/scripts/playwright_cli.sh.
  2. Run the core loop through the wrapper: open the page, snapshot, interact using refs from the latest snapshot, and snapshot again after navigation or major DOM change. Use ~/.codex/skills/playwright/references/cli.md for command reference and ~/.codex/skills/playwright/references/workflows.md for troubleshooting only when needed.
  3. Capture artifacts such as screenshots, PDFs, or traces when they help. Keep the workflow explicit and CLI-based; do not pivot into Playwright test code unless the user explicitly asked for test files.

Non-Negotiable Acceptance Criteria

  • Always snapshot before using element refs like e12.
  • Re-snapshot after navigation, modal changes, tab switches, or any UI change that could stale refs.
  • Prefer explicit CLI commands over eval/custom code when the wrapper can already do the job.
  • Use --headed when a visual check materially helps.

Output

  • A concise command sequence or workflow summary.
  • Latest relevant element refs or artifact paths when the task depends on them.
  • A short note on whether the flow succeeded, stalled on stale refs, or needs a new snapshot.

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.

Reviews can't be read right now.

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