From claude-commands
Reference guide for using the Chrome Superpowers MCP tool to control the browser (navigate, click, type, eval, screenshot). Includes React-specific workarounds for onChange handlers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-commands:chrome-superpowers-referenceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Chrome Superpowers is an **MCP (Model Context Protocol) tool**, not a local skill file.
Chrome Superpowers is an MCP (Model Context Protocol) tool, not a local skill file.
MCP Tool Name: mcp__chrome-superpower__use_browser
The Chrome Superpowers MCP is integrated into Claude Code as a native tool. You can access it through the mcp__chrome-superpower__use_browser function.
For AI Universe Frontend testing patterns, see:
~/.claude/skills/chrome-localhost3000-usage.mdCheck the tool definition in your current session for parameter details:
mcp__chrome-superpower__use_browser
- action: navigate, click, type, extract, screenshot, eval, select, attr, await_element, await_text
- selector: CSS or XPath (XPath must start with / or //)
- payload: Action-specific data
Common Actions:
navigate - Go to URLclick - Click element by selectoreval - Execute JavaScriptscreenshot - Capture screenshotawait_element - Wait for element to appearKey Limitations:
type action doesn't trigger React onChange handlerseval with native value setters and event dispatching~/.claude/skills/chrome-localhost3000-usage.md/tmp/disappearing-messages-findings.mdconvov-b2eThis is a system-provided MCP tool, not a user-created skill. The MCP server is managed by Claude Code's infrastructure, not stored in local files.
npx claudepluginhub jleechanorg/claude-commands --plugin claude-commandsAutomates Chrome browser testing via MCP tools: debugging console errors, monitoring network requests, executing JavaScript, recording GIF evidence. Requires visible browser, not for CI/CD.
Controls Chrome via DevTools Protocol for navigating, clicking, typing, multi-tab management, and content extraction with auto-screenshots.
Provides browser-level verification using Claude-in-Chrome (primary) or chrome-devtools-mcp (fallback). Includes provider detection, dev server detection, and graceful degradation.