Browser Automation

Use this for browser exploration, validation, screenshots, recordings, frontend debugging, accessibility checks, and E2E/user-flow testing. Do not delete, reset, or mutate non-test data without explicit user confirmation.

If the app cannot be started, auth is missing, or fixtures are unavailable, report BLOCKED instead of inventing passing results.

Runtime Order

1. Use built-in browser tools first when they are visible in the current Claude Code session. If the user wants Claude in Chrome and no browser tools are visible, tell them to enable claude-in-chrome with /mcp.
2. Use the project's configured browser runner when it exists.
3. Use playwright-skill only as the bundled fallback/runtime reference.
4. If no runtime is available, report BLOCKED with the missing tool/package.