Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/de:browserThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Relaunch the configured browser with remote debugging for a development environment or the main repo.
Relaunch the configured browser with remote debugging for a development environment or the main repo.
Use this when Chrome was closed and you need to reopen it with the correct --remote-debugging-port and --user-data-dir for the chrome-devtools MCP to connect.
Arguments:
[env] - Environment name (supports partial match). Omit to launch for the main repo.Examples:
/de:browser - Relaunch browser for the main repo (uses base debug port)/de:browser my-feature - Relaunch browser for 'my-feature' environment/de:browser 76 - Relaunch using partial match (e.g., matches 'fix-bug-76')Run (script is at the plugin root, two levels above this skill's base directory):
!lib/dev-env.sh browser $ARGUMENTS
After launching, tell the user:
npx claudepluginhub danielcarmingham/dev-envLaunches and configures Chrome DevTools MCP server for visual access to live browser, enabling screenshots, DOM snapshots, console debugging, network inspection, Core Web Vitals measurement, Lighthouse audits, and automation of interactions on Windows/Linux/WSL2.
Automates browser tasks via Chrome DevTools CLI: take snapshots, click, fill, navigate, and more from the terminal.
Provides browser-level verification using Claude-in-Chrome (primary) or chrome-devtools-mcp (fallback). Includes provider detection, dev server detection, and graceful degradation.