playwright

Topics in the source

• Playwright CLI Skill
• Prerequisite check (required)
• Skill path (set once)
• Quick start
• Core workflow
• When to snapshot again
• Recommended patterns
• Form fill and submit

Drive a real browser from the terminal using playwright-cli. Prefer the bundled wrapper script so the CLI works even when it is not globally installed. Treat this skill as CLI-first automation. Do not pivot to @playwright/test unless the user explicitly asks for test files. Before proposing commands, check whether npx is available (the wrapper depends on it): If it is not available, pause and ask the user to install Node.js/npm (which provides npx). Provide these steps verbatim: Once npx is present, proceed with the wrapper script. A global install of playwright-cli is optional. User-scoped skills install under $CODEXHOME/skills (default: /.codex/skills). Use the wrapper script: If the user prefers a global install, this is also valid: 1. Open the page. 2. Snapshot to get stable element refs. 3. Interact using refs from the latest snapshot. 4. Re-snapshot after navigation or significant DOM changes. 5. Capture artifacts (screenshot, pdf, traces) when useful. Minimal loop: Snapshot again after: navigation clicking elements that change the UI substantially opening/closing modals or menus tab switches Refs can go stale. When a command fails due to a missing ref, snapshot again. The wr

This is an excerpt. Refer to the complete source and its current requirements.