'devtools' 검색 결과

Use when reading state from a running PlayCanvas app, to reach its live Application through the Engine devtools hook without changing app code.

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

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

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

Redux Toolkit patterns for complex client state. Use when managing enterprise-scale state, needing DevTools, entity normalization, or RTK Query for data fetching.

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

DOM-based XSS occurs when JavaScript reads attacker-controlled sources (`location.hash`, `document.referrer`, `window.name`, `location.search`) and passes them to dangerous sinks (`document.write`, `innerHTML`, `eval`, `location.href`, `setTimeout`, `jQuery.html()`) without sanitization. Unlike reflected/stored XSS, payloads never reach the server. Detect by auditing JavaScript for tainted data flow from DOM sources to sinks. Tools: Burp Suite DOM Invader, Chrome DevTools, DOMPurify (fix).

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

Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile setup", "setup task runner", "audit taskfile", "scaffold taskfile", "add taskfile", "taskfile.yml", or "developer tasks".

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

Install Tilt and scaffold or audit Tiltfile + tilt/ configurations with ecosystem-aware templates. Auto-detects Java/Gradle (Spring Boot), Next.js, Python/uv, and external infrastructure; recommends single-file or modular tilt/*.star + service-config.yaml + environments.yaml patterns based on project complexity. Bakes in production-context safety guards, PVC persistence toggles, JDWP debug ports, and optional Prometheus/Grafana/Traefik scaffolds. Use when user runs /devtools:tilt-setup, mentions "tilt setup", "setup tilt", "scaffold tiltfile", "audit tiltfile", "tilt configure", "tilt project setup", "Tiltfile", "local kubernetes dev", or "kubernetes development environment".

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

Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".

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

Record a narrated video of a feature running in the local dev app, for a PR or a stakeholder. Drives a headless Chrome over the DevTools Protocol so clicks and keystrokes are real, captures frames, and encodes an mp4 with no extra tooling installed. Use when the user asks to "record a video", "make a demo", "show this working", or wants a screen recording of a change.

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

Target a specific Google Chrome user profile for browser automation via CDP. Discovers installed profiles from the Chrome Local State file, launches Chrome with the requested profile attached to a debug port, and connects agent-browser via `agent-browser connect <port>`. Use when "automate using my Work/Personal Chrome", "open site with my saved session", or "use Chrome profile named <name>". NOT for headless scraping without an existing user profile (use mk:agent-browser directly); NOT for importing cookies only (use agent-browser --auto-connect state save).

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

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

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

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

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

Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is this route slow", "run Lighthouse", "check for a memory leak", before any performance-gated certification (Built for Shopify, Core Web Vitals thresholds, store listing review), and before any launch or traffic-multiplier event. Measurement only — this skill never drives functional journeys.

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

Systematically find and fix performance problems in applications, frontend and backend, by measuring first. Use this skill whenever the user reports slow endpoints, high latency, poor throughput, memory leaks, large bundles, or slow page loads; wants to profile with cProfile, py-spy, Chrome DevTools, Node --cpu-prof, or perf; run load tests with locust or k6; set performance budgets or SLOs; optimize database queries (EXPLAIN, indexes, N+1); add caching (Redis); improve frontend performance (code splitting, lazy loading, image optimization, memoization, virtualization); or tune the network (CDNs, gzip/br, HTTP/2/3). Also trigger for p50/p95/p99 latency, throughput, error rate, connection pooling, async vs threads, GIL, and memory leak investigations.

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

Official GSAP skill for GSAP plugins — registration, ScrollToPlugin, ScrollSmoother, Flip, Draggable, Inertia, Observer, SplitText, ScrambleText, SVG and physics plugins, CustomEase, EasePack, CustomWiggle, CustomBounce, GSDevTools. Use when the user asks about a GSAP plugin, scroll-to, flip animations, draggable, SVG drawing, or plugin registration.

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

Automates the user's existing signed-in Chrome profile through Chrome DevTools MCP (via mcporter): inspecting pages, screenshots, forms, clicks, and running JavaScript, without AppleScript. Use when a task needs a real logged-in browser tab rather than a fresh headless one.

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

Chrome DevTools CLI for browser automation via shell commands. Use when interacting with web pages from the command line — navigating, clicking, filling forms, inspecting console/network, taking screenshots, or extracting page content. Triggers on: browse a page, automate Chrome, inspect console, check network requests, take a screenshot, fill a form, click a button.

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

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

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

Inspect, debug, and inject custom code into a running Steam client — desktop (macOS, Linux, Windows) or Steam Deck over the network — through its Chromium Embedded Framework (CEF) Chrome DevTools Protocol endpoint. Use when developing Steam UI plugins, mods, themes, or integrations — injecting CSS/JS to try a change, locating webpack modules and obfuscated class names, reading React or SteamUIStore state, inspecting Big Picture / Quick Access Menu windows, screenshotting what actually rendered, streaming console logs, or diagnosing runtime errors in Steam's UI. The same commands run against either device, or both at once. Injection is per-session and for development only. Not for building a plugin loader or making changes persist across restarts, Steamworks game SDK work, game development, or scraping the public Steam web store.

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

Playwright automation, Chrome DevTools debugging, and browser interaction testing. Use for E2E/unit tests, capturing screenshots, inspecting network/console logs, or validating user flows in web applications.

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

Next.js 16.2.4 with TypeScript — App Router, Server Components, use cache directive, Turbopack dev, Server Actions, ISR, SSR, SSG, MCP devtools, metadata API, route handlers, instrumentation.

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

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

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

React (UI ライブラリ本体, react / react-dom 19.3) の公式リファレンス。 Hooks (useState, useEffect, useActionState, useOptimistic, useEffectEvent), use, cache, Suspense, Activity, ViewTransition, createRoot, hydrateRoot, createPortal, flushSync, react-dom/server, Server Components / Server Functions, React Compiler, eslint-plugin-react-hooks, DevTools, Rules of React。React Router・Next.js・TanStack 系・RHF とは別。

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

React Native (Meta 製クロスプラットフォームネイティブアプリフレームワーク, react-native 0.87 / 0.88) の リファレンス。View, Text, FlatList, Pressable, TextInput, Animated, StyleSheet, Flexbox, Platform, New Architecture (Fabric, TurboModules, Codegen), Hermes, Metro, Fast Refresh, TypeScript, React Native DevTools, Android / iOS 統合、upgrade (Upgrade Helper)・0.84〜0.88 差分。

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

Flutter (Google 製 Dart クロスプラットフォーム UI フレームワーク, 3.47) のリファレンス。 StatelessWidget / StatefulWidget / BuildContext, Sliver, Material / Cupertino, Impeller, flutter CLI, pubspec.yaml, hot reload, flutter fix / dart fix, DevTools, Widget Previewer, MVVM, platform channels / dart:ffi, add-to-app, Flutter Web / Wasm, GenUI SDK / AI Toolkit。

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