メニュー
Use Chrome DevTools Protocol through Playwright to capture richer browser diagnostics such as console errors, failed requests, coverage, and performance metrics when normal logs are insufficient.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Turn a specification into a concrete architecture with stable contracts, file boundaries, ownership, and risk analysis. Use this when acting as the architecture writer for a task.
Run the project verification stack after code changes. Trigger on code changes and stop on the first failure, fix it, then rerun the full stack from the top.
Verify that newly created files follow the repo's existing directory layout, naming conventions, and export patterns. Trigger when a new file is created.
Break architecture into execution-ready sub-tasks with clear ownership, dependencies, and contract references. Use this when acting as the planner for a task.
Use Playwright for browser automation, UI validation, E2E tests, and interaction debugging. Useful for flows that need real page navigation, assertions, screenshots, or request interception.
Final merge-readiness check after gates pass. Confirms verification is green, changed files are clean, and obvious release blockers are gone before merge.
| name | chrome-devtools-debugging |
| description | Use Chrome DevTools Protocol through Playwright to capture richer browser diagnostics such as console errors, failed requests, coverage, and performance metrics when normal logs are insufficient. |
| owner | any |
| trigger | null |
| version | 2 |
Use this when browser issues need deeper diagnostics than standard Playwright assertions or console output.
references/chrome-devtools-recipes.md when you need concrete CDP snippets for console capture, failed requests, performance metrics, or JS coverage.Start with the smallest useful capture and add more only when needed.