Skip to content
browser-dev-tools logo

Browser Dev Tools

browser-dev-tools

This skill should be used when working with browser-rendered artifacts (i.e. Bun, React/React Native) to proactively validate that development work on localhost is being built appropriately and to support debugging browser-rendered content. Use this skill after making frontend changes to verify t...

mattnigh/skills_collection0installs24stars

SKILL.md

Full skill instructions

Browser Dev Tools

Overview

This skill provides Chrome DevTools Protocol tools for validating and debugging browser-rendered artifacts during development. Use these tools to verify that localhost servers are rendering correctly and to debug visual issues proactively.

The tools connect to Chrome running on port :9222 with remote debugging enabled.

When to Use This Skill

Use this skill proactively in these scenarios:

  1. After making frontend code changes - Validate that React, Bun, HTML, or other frontend code renders correctly on localhost
  2. After starting a dev server - Verify the application loads and displays properly
  3. When debugging browser rendering issues - Inspect page state, DOM structure, or cookies
  4. When validating UI changes - Take screenshots to visually confirm changes appear as expected

Important: Always use this skill proactively after completing frontend development tasks to validate the work before considering it done.

Available Tools

All browser tools are located in ~/​.claude/​skills/​browser-dev-tools/​tools/ and should be executed via the Bash tool.

Start Chrome

~/​.claude/​skills/​browser-dev-tools/​tools/​browser-start.js                # Fresh profile
~/​.claude/​skills/​browser-dev-tools/​tools/​browser-start.js --profile      # Auto-detect profile
~/​.claude/​skills/​browser-dev-tools/​tools/​browser-start.js --profile "Profile 2"  # Specific profile

Launch Chrome with remote debugging.

Profile Auto-Detection:

  • When using --profile without a profile name, the script automatically selects the appropriate Chrome profile based on the current working directory:
  • You can override this by specifying a profile name: --profile "Profile 2"

Important: Always use --profile (auto-detect) or specify a profile when you need to preserve authentication state for testing authenticated pages.

Navigate

~/​.claude/​skills/​browser-dev-tools/​tools/​browser-nav.js http://localhost:3000
~/​.claude/​skills/​browser-dev-tools/​tools/​browser-nav.js http://localhost:3000 --new

Navigate to URLs. Use --new flag to open in a new tab instead of reusing the current tab.

Screenshot

~/​.claude/​skills/​browser-dev-tools/​tools/​browser-screenshot.js

Capture the current viewport and return a temporary file path. Always take screenshots after navigating to validate the rendered output visually.

Evaluate JavaScript

~/​.claude/​skills/​browser-dev-tools/​tools/​browser-eval.js 'document.title'
~/​.claude/​skills/​browser-dev-tools/​tools/​browser-eval.js 'document.querySelectorAll("a").length'

Execute JavaScript in the active tab to extract data, inspect page state, or perform DOM operations programmatically.

Pick Elements

~/​.claude/​skills/​browser-dev-tools/​tools/​browser-pick.js "Click the submit button"

Launch an interactive picker that lets the user click elements to select them. The user can select multiple elements (Cmd/​Ctrl+Click) and press Enter when done. Returns CSS selectors for the selected elements.

Use this when the user wants to select specific DOM elements on the page.

Cookies

~/​.claude/​skills/​browser-dev-tools/​tools/​browser-cookies.js

Display all cookies for the current tab including domain, path, httpOnly, and secure flags. Use this to debug authentication issues or inspect session state.

Common Workflows

Validating Frontend Changes (Primary Use Case)

After making changes to frontend code (React components, HTML, CSS, etc.):

  1. Start Chrome if not already running:

    ~/​.claude/​skills/​browser-dev-tools/​tools/​browser-start.js --profile  # Auto-detects profile
    

    Note: Use --profile to auto-detect the appropriate profile based on cwd (personal vs work).

  2. Navigate to localhost:

    ~/​.claude/​skills/​browser-dev-tools/​tools/​browser-nav.js http://localhost:PORT
    

    Replace PORT with the appropriate port (e.g., 3000, 5173, 8080).

  3. Take a screenshot:

    ~/​.claude/​skills/​browser-dev-tools/​tools/​browser-screenshot.js
    
  4. Read the screenshot using the Read tool to visually validate the changes.

  5. If issues are found, use JavaScript evaluation to inspect the page state:

    ~/​.claude/​skills/​browser-dev-tools/​tools/​browser-eval.js 'document.body.innerHTML'
    

Debugging Rendering Issues

When troubleshooting why something isn't rendering correctly:

  1. Navigate to the problematic page

  2. Take a screenshot to see the current state

  3. Evaluate JavaScript to inspect:

    • DOM structure: document.querySelector('#myElement')
    • Console errors: console.log(...)
    • Element properties: document.querySelector('#myElement').style
  4. Check cookies if authentication or session issues are suspected

Best Practices

  • Always validate proactively - Take screenshots after frontend changes to catch visual issues early
  • Use profile auto-detection - Use --profile (without arguments) to automatically load the correct profile based on your working directory (personal vs work)
  • Navigate before evaluating - Ensure the page is loaded before running JavaScript
  • Read screenshots - Always use the Read tool on screenshot paths to view the captured image
  • Check common ports - Typical dev servers run on 3000 (React/​Next.js), 5173 (Vite), 8080 (generic), or 4200 (Angular)

More skills from mattnigh

spring-framework-patterns logo
mattnigh/skills_collection

spring-framework-patterns

Comprehensive Spring Framework and Spring Boot best practices including dependency injection patterns, bean lifecycle and scopes, REST API development, Spring Data JPA, service layer design, Spring Security, testing strategies, caching, AOP, async processing, error handling, and common anti-patte...

24 0
View

TypeScript厳格モードによる型安全性設計を専門とするスキル。 📖 参照書籍: - 『Effective TypeScript』(Dan Vanderkam): 型設計 📚 リソース参照: - `resources/Level1_basics.md`: レベル1の基礎ガイド - `resources/Level2_intermediate.md`: レベル2の実務ガイド - `resources/Level3_advanced.md`: レベル3の応用ガイド - `resources/Level4_expert.md`: レベル4の専門ガイド - `resources/di...

24 0
View
deploying-cloud-k8s logo
mattnigh/skills_collection

deploying-cloud-k8s

Deploys applications to cloud Kubernetes (AKS/GKE/DOKS) with CI/CD pipelines. Use when deploying to production, setting up GitHub Actions, troubleshooting deployments. Covers build-time vs runtime vars, architecture matching, and battle-tested debugging.

24 0
View
moai-alfred-agent-guide logo
mattnigh/skills_collection

moai-alfred-agent-guide

19-agent team structure, decision trees for agent selection, Haiku vs Sonnet model selection, and agent collaboration principles. Use when deciding which sub-agent to invoke, understanding team responsibilities, or learning multi-agent orchestration.

24 0
View
mermaid-diagram-generator logo
mattnigh/skills_collection

mermaid-diagram-generator

Converts architecture descriptions, module specs, or workflow docs into Mermaid diagrams. Use when visualizing brick module relationships, workflows (DDD, investigation), or system architecture. Supports: flowcharts, sequence diagrams, class diagrams, state machines, entity relationship diagrams,...

24 0
View
pre-flight-check logo
mattnigh/skills_collection

pre-flight-check

INVOKE FIRST before any code work. Validates git workflow (branch, issue, worklog) and checks approach. Use at START of every task and END before completing. Prevents skipped steps.

24 0
View
lead-dev logo
mattnigh/skills_collection

lead-dev

Lead Développeur - Coordination technique opérationnelle, code review, mentoring et livraison. Pair de web-dev-process au niveau OPÉRATIONS.

24 0
View
worker-monitor logo
mattnigh/skills_collection

worker-monitor

Monitor Docker workers, RQ queue health, and auto-scale workers (max 4). Use when: checking job progress, monitoring queue depth, scaling workers up/down, diagnosing slow processing, or waiting for jobs to complete. Referenced by data-quality skill during reprocessing.

24 0
View
quality-advisor logo
mattnigh/skills_collection

quality-advisor

Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality

24 0
View
bump-version logo
mattnigh/skills_collection

bump-version

This skill should be used when the user wants to bump the version number in the workspace. It updates versions across all pyproject.toml files (root, tde, and tda packages) and the CHANGELOG.md to keep them synchronized.

24 0
View
check-code-quality logo
mattnigh/skills_collection

check-code-quality

Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.

24 0
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View