playwrightlisted

# Playwright MCP Skill This is not the default browser surface. For local app checks, screenshots, ordinary page inspection, or tasks that do not require the user's active Chrome session, prefer Codex `Browser` / in-app browser in the background. For tasks that need the user's Chrome login state or existing tabs, prefer the Codex Chrome plugin before Playwright. Use Playwright as the reliable browser execution fallback in this stack: - HTTP/API or static extraction: default first choice when it can answer the task - Codex Browser / in-app browser: default browser surface for local pages and ordinary page inspection - Codex Chrome plugin: logged-in Chrome profile, existing tabs, and extension-backed interaction - `playwright-ext`: explicit fallback only after manual enablement When this skill is deliberately selected, use a single channel only: - Use `playwright-ext` MCP inside this skill only when `codex mcp get playwright-ext` reports it is enabled. - Do not use `playwright-cli` wrapper in this skill. - Do not pivot to `@playwright/test` unless the user explicitly asks for test files. ## Role In The Stack Choose Playwright when: - the user explicitly asks to use Playwright Extension or a real Chrome extension session. - the Codex Chrome plugin cannot complete the action and Playwright has been manually enabled. - the workflow is interaction-heavy and must be verified step by step. - success depends on stable refs, precise DOM transitions, or repeated re-snapshot control