القائمة
Use guided Chrome DevTools MCP setup and workflows for browser runtime debugging. Use when a web app needs console, network, DOM, accessibility, Lighthouse, performance, responsive, or live-browser investigation beyond normal tests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose failed or unreliable agent workflows by classifying bad assumptions, missing observations, tool misuse, wrapper failures, hidden repair loops, incomplete validation, handoff gaps, and repeated failure patterns. Use after a failed harness run, flaky agent output, or confusing validation loop.
Review agent-generated changes against project rules. Use when asked for a review, before opening a PR, after large Codex edits, or when checking diffs for correctness, security, architecture, tests, docs drift, dependencies, migrations, and release risk.
Generate or maintain a minimal high-signal AGENTS.md for coding agents. Use whenever a repo needs agent instructions, an existing AGENTS.md is too long or vague, or project docs/scripts need a concise routing map for Codex.
Define and mechanically enforce architecture boundaries for a repo. Use when a project needs allowed dependency rules, forbidden imports, layer documentation, dependency maps, circular dependency checks, or protection against agent-created architectural drift.
Scaffold a new TypeScript web, mobile, API, or full-stack project with Better-T-Stack, then harden it with the Pax Fullstack Harness. Use whenever the user wants a new TypeScript app scaffold, mentions Better-T-Stack, asks for a modern type-safe stack, or wants Codex to start a repo that is agent-ready from day one.
Build PR validation, local CI reproduction, CI triage, and deployment gates. Use when a repo needs GitHub Actions beyond basic validation, coverage/artifact expectations, branch protection notes, CI failure triage docs, or release/deployment readiness gates.
| name | chrome-devtools-runtime-debugger |
| description | Use guided Chrome DevTools MCP setup and workflows for browser runtime debugging. Use when a web app needs console, network, DOM, accessibility, Lighthouse, performance, responsive, or live-browser investigation beyond normal tests. |
Give agents a repeatable path for observing real browser behavior through Chrome DevTools MCP without bundling global MCP config into this plugin.
Choose the right browser tool.
$click-path-and-browser-qa to turn repeated browser workflows into route/control inventories and Playwright coverage.Guide setup when missing.
scripts/check_chrome_devtools_mcp.py when available to check whether chrome-devtools is configured.codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest.Run diagnosis.
Document findings.
docs/observability/browser-debugging.md from assets/templates/chrome-devtools-debugging.md.tmpl.observability-harness, testing-strategy-builder, or tdd-playwright-workflow follow-up checks.sprint-contract-observability.codex mcp list; if unavailable, provide setup guidance instead of pretending the tool is callable.