Browser Testing With Devtools

Use only when the user explicitly requests live browser or DevTools evidence—such as DOM, console, network, screenshot, focus, accessibility, or runtime-performance observation—or when an active owner identifies a browser-only evidence gap. Requires an already configured and explicitly authorized browser/DevTools channel. Do not use merely because work targets a browser, is long, or a browser tool exists; do not use for UI design, test strategy, root-cause debugging, performance optimization, completion review, or host runtime/tool issues.

Chrike Updated 1 repo stars

File contents

Chrike/coding-agent-skills commit d67419a7d0

Frequently asked questions

npx get-skill add chrike/browser-testing-with-devtools