playwright▌

Terminal-driven browser automation with element snapshots and interactive UI workflows. \n \n Operates via playwright-cli wrapper script (requires npx ); supports headless and headed modes for visual debugging \n Core workflow: open page, snapshot for stable element references, interact using refs, re-snapshot after navigation or DOM changes \n Includes form filling, clicking, typing, multi-tab management, screenshot/PDF capture, and trace recording for flow debugging \n Element refs (e.g., e3 ,

Custom Playwright scripts for any browser automation task, with auto-detected dev servers and visible browser execution. \n \n Auto-detects running localhost dev servers; writes test scripts to /tmp to avoid project clutter \n Supports responsive design testing, login flows, form filling, link validation, and screenshot capture across multiple viewports \n Includes helper utilities for safe clicks, typed input, cookie banner handling, and table data extraction \n Configurable custom HTTP headers

Browser automation with Playwright MCP for web navigation, form interaction, and data extraction. \n \n Supports navigation, element interaction (click, type, select), screenshots, and accessibility snapshots that return element references for precise targeting \n Includes JavaScript execution via browser_evaluate and multi-step atomic operations through browser_run_code for complex workflows \n Requires --shared-browser-context flag to maintain browser state across sequential commands; server r

Cross-browser end-to-end testing with auto-wait, parallel execution, and built-in debugging tools. \n \n Supports Chromium, Firefox, and WebKit across desktop and mobile devices with automatic element waiting and network control \n Includes role-based locators, page object model patterns, and storage-state authentication for maintainable test suites \n Offers visual regression testing via screenshot comparison, video recording, and trace viewer for debugging failed tests \n Built-in test runner

Use this skill when you need to:

Set TARGET_URL to the app you are debugging. Use port 4444 and prefer 127.0.0.1 over localhost.