'dev tool' 검색 결과

Build Claude Code plugin hooks: automated checks triggered by tool use or session events. Get guidance on prompt and command hooks for validating actions, checking task completion, loading context, and testing configurations.

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

• Checking dangerous commands before execution
• Verifying completion before the agent stops
• Loading project context when a session starts

Set up language servers, programs that help tools understand source code, for Go, TypeScript, Python, and Rust. Check missing prerequisites, install them with approval, and verify the lsp tool against a real source file.

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

• Enable language support for the lsp tool
• Install a missing language server
• Set up prerequisite development tools

Build Claude Code plugin hooks: automated checks triggered by tool use or session events. Get guidance on prompt and command hooks for validating actions, checking task completion, loading context, and testing configurations.

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

• Checking dangerous commands before execution
• Verifying completion before the agent stops
• Loading project context when a session starts

Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.

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

Best practices for Docker-based ROS2 development including multi-stage Dockerfiles, docker-compose for multi-container robotic systems, DDS discovery across containers, GPU passthrough for perception, and dev-vs-deploy container patterns. Use this skill when containerizing ROS2 workspaces, setting up docker-compose for robot software stacks, debugging DDS communication between containers, configuring NVIDIA Container Toolkit for GPU workloads, forwarding X11/Wayland for rviz2 and GUI tools, or managing USB device passthrough for cameras and serial devices. Trigger whenever the user mentions Docker with ROS2, docker-compose for robots, Dockerfile for colcon workspaces, container networking for DDS, devcontainer for ROS2, multi-stage builds for ROS2, or deploying ROS2 in containers. Also trigger for CI/CD with Docker-based ROS2 builds, CycloneDDS or FastDDS configuration in containers, or shared memory in Docker. Covers Humble, Jazzy, and Rolling distributions across Ubuntu 22.04 and 24.04 base images.

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

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

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

Install bioinformatics tools for ENCODE data analysis. Covers CLI tools (BWA, STAR, samtools, MACS2), R/Bioconductor packages (DESeq2, Seurat, ChIPseeker), Python packages (Scanpy, deeptools), and Nextflow pipeline infrastructure. Generates conda environments, R install scripts, and Python requirements. Use when the user needs to set up a bioinformatics workstation, install tools for a specific assay, create reproducible environments, or troubleshoot dependency issues. Trigger on: install tools, set up environment, conda create, bioinformatics setup, install R packages, install Bioconductor, install pipeline tools.

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

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

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

Run build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated to MAUI. INVOKES: maui devflow CLI, dotnet CLI, Android adb/android tools, and Apple simctl tools.

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

API와 개발 도구 계획을 개발자의 관점에서 대화하며 검토합니다. 경쟁 제품과의 차이와 도입 과정의 장애물을 정리하고 목적에 맞게 개선점을 살펴봅니다.

• API나 SDK 계획 재검토
• 개발자의 초기 도입 장애물 확인
• 경쟁 제품과 개발자 경험 비교

OmniRoute CLI에서 MCP 서버 상태와 도구 권한 범위를 확인합니다. 서버를 활성화·중지·재시작하고 JSON 인수로 도구를 호출합니다.

• MCP 서버 실행 상태 확인
• 서버 활성화·중지·재시작
• 도구의 권한 범위 조회

Find and fix JavaScript memory leaks that accumulate as people use a web app. Review event listeners, timers, retained page elements, and outdated asynchronous tasks, then explain how to verify cleanup in the browser.

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

• Investigating rising memory use during long sessions
• Reviewing cleanup when components are removed
• Canceling outdated requests after view changes

Measure how Google Tag Manager affects page loading and rendering. Identify costly tags, triggers, and requests, then guide cleanup, asynchronous loading, or a move to server-side processing based on observed performance problems.

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

• Investigate slow pages using GTM
• Review unused tags and triggers
• Check asynchronous script loading

Measure the size and nesting of a page's DOM, the tree of HTML elements. Identify unnecessary wrappers and oversized lists, then simplify the structure or render only visible list items to reduce confirmed rendering costs.

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

• Investigating pages with slow rendering or interactions
• Measuring HTML element counts and nesting depth
• Removing unnecessary wrapper elements

Review images needed when a page first opens, checking file size, display dimensions, and loading priority. Identify changes to preload settings and lazy loading that help the main visual content appear sooner.

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

• Reviewing hero image loading priority
• Finding lazy-loaded images in the initial viewport
• Checking image fixes in DevTools

Review how pages return from the browser’s back/forward cache, which restores them from memory. Identify event handlers that block restoration, fix lifecycle assumptions, and refresh time-sensitive information when a cached page resumes.

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

• Investigating slow back and forward navigation
• Finding event handlers that block cache restoration
• Fixing stale information after a page resumes

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

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

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Verify a local OpenSEO MCP server, which exposes tools to AI agents, through real DataForSEO calls and a headless Claude trial. Check protocol correctness alongside tool discovery, input rules, response size, errors, and asynchronous task recovery.

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

• Checking an MCP tool after adding or changing it
• Testing whether an agent can choose tools from their descriptions
• Verifying queued tasks and recovery using taskId

Set up and run Happy components locally, including its CLI, server, mobile app, and desktop app. The guide covers building, testing, checking logs, and separating development data using pnpm, the project's package management tool.

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

• Setting up a local Happy development environment
• Rebuilding the CLI and checking its daemon
• Running the server and app locally

Helps build AI features in Go with Genkit, including text generation, structured data output, streaming, tool calls, and conversational agents. Guides HTTP serving and trace inspection to check model responses and tool execution.

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

• Adding text generation or structured output to a Go app
• Building a chatbot that retains conversation state
• Connecting model responses to tool calls

Develop and debug LangBot's backend and web frontend. The skill guides environment setup, API additions, authentication, database migrations, and testing, including updates to matching MCP tools so agents can use changed API features.

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

• Set up the LangBot backend and frontend for development
• Add an API endpoint and its matching MCP tool
• Update the database schema with Alembic

Build, refactor, and troubleshoot ChatGPT apps with an MCP server, which exposes tools to the assistant, and an interactive widget. Use official documentation and examples to plan tools, scaffold code, configure security settings, and validate local operation.

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

• Scaffolding a ChatGPT app with a server and widget
• Planning app tools and their inputs
• Refactoring an existing Apps SDK demo

Set up an iPolloWork development environment in a Daytona cloud sandbox and access the real Electron app through a browser. Follow procedures for connection URLs, logs, restarts, code updates, and common startup problems.

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

• Launch a cloud development environment for iPolloWork
• Operate the Electron app through a browser
• Check logs and troubleshoot startup problems

Inspect and control live Chrome pages to investigate display problems, console errors, failed requests, and slow loading. Capture screenshots, automate page interactions, and record performance traces to identify where delays or layout shifts occur.

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

• Investigating page errors and failed network requests
• Finding causes of slow loading and layout shifts
• Capturing screenshots of pages or individual elements