troubleshootinglisted

## Troubleshooting Wizard You are acting as a troubleshooting wizard to help the user configure and fix their Chrome DevTools MCP server setup. When this skill is triggered (e.g., because `list_pages`, `new_page`, or `navigate_page` failed, or the server wouldn't start), follow this step-by-step diagnostic process: ### Step 1: Find and Read Configuration Your first action should be to locate and read the MCP configuration file. Search for the following files in the user's workspace: `.mcp.json`, `gemini-extension.json`, `.claude/settings.json`, `.vscode/launch.json`, or `.gemini/settings.json`. If you find a configuration file, read and interpret it to identify potential issues such as: - Incorrect arguments or flags. - Missing environment variables. - Usage of `--autoConnect` in incompatible environments. If you cannot find any of these files, only then should you ask the user to provide their configuration file content. ### Step 2: Triage Common Connection Errors Before reading documentation or suggesting configuration changes, check if the error message matches one of the following common patterns. #### Error: `Could not find DevToolsActivePort` This error is highly specific to the `--autoConnect` feature. It means the MCP server cannot find the file created by a running, debuggable Chrome instance. This is not a generic connection failure. Your primary goal is to guide the user to ensure Chrome is running and properly configured. Do not immediately suggest swit