'devtools' 검색 결과

Capture an entire web page as a full-page screenshot using Chrome DevTools Protocol, Chrome's developer control interface. The workflow needs no additional dependencies and provides page images for portfolios, case studies, and audit reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Capturing website images for a portfolio
• Preparing full-page images for case studies
• Recording page appearances for an audit report

Audit web images that are larger than their displayed size and help serve suitable versions for different screens. Review image dimensions, responsive image settings, and Lighthouse findings, then provide updated HTML and steps to verify the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding oversized images on mobile pages
• Reviewing srcset and sizes against the actual layout
• Adding image variants for different screen widths

Review early connections to third-party services such as fonts and APIs. Use loading measurements to identify essential domains, recommend preconnect hints that prepare connections in advance, and remove unnecessary hints that add overhead.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating connection delays for external fonts and APIs
• Reviewing preconnect hints in the page head
• Removing unnecessary early connections

Audit a page’s HTTP requests to find unnecessary network activity behind slow loading. Confirm bottlenecks with performance measurements, then suggest changes such as combining files, grouping icons, or embedding resources needed for the initial display.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow initial page loads
• Finding unnecessary requests for images, CSS, and JavaScript
• Planning file consolidation and icon sprites

Investigate slow page loads and check whether resources use HTTP/2 or HTTP/3. Measure the actual bottleneck, then recommend server or CDN changes where appropriate, explaining how shared connections and compressed headers affect loading.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow page loads
• Checking the HTTP protocol used for resources
• Reviewing web server or CDN settings

Measure how quickly a webpage updates after user interactions using INP, a responsiveness metric. Identify confirmed bottlenecks and improve event handlers, split long tasks, or move heavy computation to web workers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow responses to clicks and other interactions
• Reviewing event handlers and long tasks using measurements
• Considering web workers for heavy computation

Find broken or fragile image references in markup, styles, and components. Correct paths, restore missing assets, and add fallback images, then verify how the page behaves when image requests fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find why product images are missing
• Check image paths after a build
• Add fallback images for external URLs

Audit page speed in a real browser to find delays in loading, script execution, and layout. Use measured results to identify bottlenecks, compare device and connection conditions, and guide performance improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find the causes of slow page loading
• Compare performance across device and connection simulations
• Add browser performance audits to development and CI/CD

Audit slow page loads by measuring how static files, such as images and scripts, are delivered. Check CDN usage, a network of distributed servers, and identify caching or delivery settings that need improvement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow page loads
• Checking CDN delivery of images and scripts
• Reviewing caching settings for global audiences

Investigate growing memory usage in Qwen Code CLI by comparing heap snapshots, records of objects in memory. Trace what keeps objects alive, identify likely causes, and repeat the workload to verify a fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating steadily growing memory usage
• Tracing references that keep objects alive
• Finding growing arrays, caches, or event listeners

Debug json-render interfaces with an inspector panel that shows screen specifications, editable runtime state, action history, and streamed updates. Select a rendered page element to locate its definition and investigate display or interaction problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate missing or incorrectly displayed elements
• Inspect and edit application state at runtime
• Review action results and errors

Plan, implement, or review chrome devtools work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests chrome devtools work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify web apps with browser DevTools—DOM, console, network, performance, and accessibility at runtime. Use with Chrome DevTools MCP or headless browser tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill provides guidance for using Chrome DevTools MCP for browser debugging and automation. Use when debugging web pages, analyzing performance, inspecting network requests, viewing console messages, or interacting with Chrome DevTools features programmatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Uses the chrome-devtools-axi CLI for browser automation, accessibility-tree snapshots, console and network inspection, screenshots, Lighthouse audits, and performance traces. Use when interacting with Chrome from the shell, especially when the user mentions chrome-devtools-axi, AX snapshots, browser debugging, or DevTools automation from the command line.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Node.js 실행을 일시 중지하고 변수와 실행 경로를 조사합니다. 비동기 작업 중단, 간헐적 테스트 실패, 메모리 증가와 CPU 부하의 원인을 찾는 데 사용합니다.

• 비동기 작업이 멈추는 원인 조사
• 간헐적으로 실패하는 테스트 조사
• 시작 시점과 자식 프로세스 문제 조사

Build web animations with GSAP plugins for text, SVG graphics, dragging, scrolling, and layout changes. It guides plugin selection, registration, configuration, and cleanup, with examples for implementing effects and reviewing existing animation code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Animating headings one character or line at a time
• Adding SVG drawing and shape transitions
• Building drag interactions with momentum

Find CSS and JavaScript that delay a page’s first visible content. Confirm the bottleneck with browser tools or performance data, then adjust loading behavior and inline essential styles to help the page start rendering sooner.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a blank screen during page loading
• Reviewing CSS and JavaScript loading behavior
• Inlining styles needed for the initial display

Measure page loading speed and identify what prevents a page from loading in under three seconds. Use performance measurements to guide improvements such as lazy loading, caching, CDN delivery, and reducing resource costs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow page loads
• Finding heavy resources and costly rendering steps
• Checking performance on a throttled 3G connection

Audit page loading and choose resource hints, browser instructions for fetching files or preparing connections early. Use measurements to identify delays, then suggest preload, preconnect, prefetch, or dns-prefetch for critical assets, external services, and likely next-page resources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing early loading of key images and fonts
• Preparing connections to external services
• Prefetching resources for likely next pages

Review slow page loads and choose resource hints, browser instructions that start loading or connecting earlier. Use measurements to identify bottlenecks, then recommend preload, preconnect, prefetch, or dns-prefetch for important assets and likely next-page resources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing slow loading of prominent images and fonts
• Preparing connections to external services
• Prefetching resources for likely next-page visits