vcchrome-devtools

# Chrome DevTools Agent Skill Browser automation via Puppeteer scripts with persistent sessions. All scripts output JSON. ## Skill Location Skills can exist in **project-scope** or **user-scope**. Priority: project-scope > user-scope. ```bash # Detect skill location (no cd needed - scripts use __dirname for paths) SKILL_DIR="" if [ -d ".claude/skills/chrome-devtools/scripts" ]; then SKILL_DIR=".claude/skills/chrome-devtools/scripts" elif [ -d "$HOME/.claude/skills/chrome-devtools/scripts" ]; then SKILL_DIR="$HOME/.claude/skills/chrome-devtools/scripts" fi # Run scripts with full path: node "$SKILL_DIR/script.js" --args ``` ## Choosing Your Approach | Scenario | Approach | |----------|----------| | **Source-available sites** | Read source code first, write selectors directly | | **Unknown layouts** | Use `aria-snapshot.js` for semantic discovery | | **Visual inspection** | Take screenshots to verify rendering | | **Debug issues** | Collect console logs, analyze with session storage | | **Accessibility audit** | Use ARIA snapshot for semantic structure analysis | ## Project-Specific Setup For project-specific connection patterns and when to prefer chrome-devtools over agent-browser or docker exec, see `process/context/tests/all-tests.md` in the consuming repo. This skill file is a generic tool reference only. --- ## Automation Browsing Running Mode Browser visibility is resolved automatically by `resolveHeadless()` in `lib/browser.js`: | Environment | Default | ...