agentleFS
vibe-cokitvibe-cokit/claude-code/skills/chrome-devtools/SKILL.md

chrome-devtools

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Inspect and profile a running page via Puppeteer/CDP scripts. Triggers on: console or JS errors on a page, failing network requests, Core Web Vitals profiling, WebSocket debugging, ARIA tree inspection. Cross-browser E2E tests are `playwright`.

  • Installs packages

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aesthetic, web-frameworks and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mrgoonieSkill

    aesthetic

    Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.

    Also in 5 projects that use this

  • mrgoonieSkill

    web-frameworks

    Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.

    Also in 8 projects that use this

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 4 projects that use this

  • truongtv22Skill

    mobile-development

    Build modern mobile applications with React Native, Flutter, Swift/SwiftUI, and Kotlin/Jetpack Compose. Covers mobile-first design principles, performance optimization (battery, memory, network), offline-first architecture, platform-specific guidelines (iOS HIG, Material Design), testing strategies, security best practices, accessibility, app store deployment, and mobile development mindset. Use when building mobile apps, implementing mobile UX patterns, optimizing for mobile constraints, or making native vs cross-platform decisions.

    Also in 5 projects that use this

  • +6 more from mrgoonie

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Linux/WSL only: run "$SKILL_DIR/install-deps.sh" first for Chrome system libraries.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chrome DevTools

Single-purpose Puppeteer scripts over one persistent browser session. Every script prints JSON.

Scope: live-page inspection and profiling (CDP domains, console, network, vitals, WebSockets). Not a test runner — playwright owns cross-browser E2E suites and assertions.

Setup

# Resolve skill dir (project scope wins over user scope; scripts use __dirname, no cd needed)
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

npm install --prefix "$SKILL_DIR"          # one-time
node "$SKILL_DIR/navigate.js" --url https://example.com
# {"success": true, "url": "...", "title": "..."}

Linux/WSL only: run "$SKILL_DIR/install-deps.sh" first for Chrome system libraries.

Headless policy: headless only on Linux/WSL/CI; headed on macOS/Windows for debuggability. Run several sessions in parallel to simulate multiple users or device classes.

Session persistence

Browser state survives across script calls via .browser-session.json (WebSocket endpoint). Scripts disconnect but leave the browser running.

node "$SKILL_DIR/navigate.js" --url https://example.com/login
node "$SKILL_DIR/fill.js" --selector "#email" --value "user@example.com"
node "$SKILL_DIR/click.js" --selector "button[type=submit]"
node "$SKILL_DIR/navigate.js" --url about:blank --close true   # end session

Scripts

navigate · screenshot · click · fill · evaluate · snapshot · aria-snapshot · select-ref · console · network · performance · ws-debug · ws-full-debug · inject-auth

Full flags, selector syntax (CSS + XPath), and output schemas: ./scripts/README.md.

Shared options: --headless false, --close true, --timeout 30000, --wait-until networkidle2.

Choosing an approach

ScenarioApproach
Source-available siteRead the source, write selectors directly
Unknown layoutaria-snapshot.js for semantic discovery → interact by [ref=eN]
Visual checkscreenshot.js (auto-compresses >5MB)
Runtime bugconsole.js + network.js into a log session, then correlate
Perf regressionperformance.js → .vitals, then references/performance-guide.md
Accessibility auditaria-snapshot.js semantic tree

Loop

Execute one focused script → read its JSON → assess → decide next action → repeat.

Artifacts live under <project>/.claude/chrome-devtools/{screenshots,snapshots,logs,tmp}/.

References

  • references/aria-snapshot.md — ARIA tree, notation table, ref-based interaction, selector discovery
  • references/recipes-and-troubleshooting.md — custom scripts, scraping/form/perf recipes, log sessions, error recovery, troubleshooting table, local-file serving
  • references/cdp-domains.md — Chrome DevTools Protocol domains
  • references/puppeteer-reference.md — Puppeteer API patterns
  • references/performance-guide.md — Core Web Vitals optimization
  • scripts/README.md — per-script options and installation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.