Skill Instructions
Purpose
Provide a repeatable way to use Chrome DevTools during website work to validate rendering, diagnose layout/CSS issues, and troubleshoot together with the Maintainer.
Hard Rules
Must
- • Use
io.github.chromedevtools/chrome-devtools-mcp/*tools when diagnosing rendering/layout issues. - • Capture concrete findings (console errors, computed styles, DOM structure) and summarize them in the PR/issue.
Must Not
- • Do not guess at rendering behavior when you can verify it using DevTools.
Golden Example
text
Use Chrome DevTools MCP tools to: - Inspect computed styles and layout for a problematic element - Check console for errors - Verify responsive behavior by simulating viewports
Actions
- •Ensure the site is available via the VS Code preview server (
http://127.0.0.1:3000/website/), then load the relevant page URL in Chrome DevTools MCP so you can inspect it. - •Use Chrome DevTools MCP tools to inspect:
- •DOM structure and element attributes
- •Computed CSS and layout metrics
- •Console logs and runtime errors
- •Network requests (if applicable)
- •Share findings with the Maintainer and propose the smallest fix.