'handler' 검색 결과

Review frequent JavaScript events and apply debounce, which waits until activity stops, or throttle, which limits execution frequency. Identify handlers causing sluggish interfaces or excessive API calls, and define browser checks for the fixes.

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

• Reduce repeated API calls from search inputs
• Review scroll and resize performance
• Choose between debounce and throttle

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

Connect syncable entity components within Twenty server internals and expose them through GraphQL, an API query interface. It guides NestJS module registration, business services, response data conversion, and consistent handling of validation and execution errors.

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

• Register builders, validators, and action handlers in NestJS modules
• Connect entity creation to validation and migration execution
• Expose entities through GraphQL with response data conversion

Turn an OpenAPI specification, a document describing an API, into an application using the chosen framework. Generate request handlers, data models, authentication, validation, tests, and setup instructions, with database access code where applicable.

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

• Build an API application from an existing specification
• Generate data models and request handlers together
• Prepare tests and setup documentation for a new project

Implement and customize managed CopilotKit Channels so agents can reply in Slack or Microsoft Teams. It covers channel handlers, persistent runtime connections, Teams setup, and checks for silent failures such as missing permissions or incompatible package versions.

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

• Customizing mention and reaction handlers
• Adding a managed Channel to an existing project
• Setting up a Microsoft Teams connection

Integrate Zoom Virtual Agent into an iOS app using WKWebView, an embedded web browser. Covers Swift and Objective-C configuration injection, messages exchanged with web content, support handoff handling, and rules for opening links.

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

• Embedding Zoom Virtual Agent in an iOS app
• Injecting configuration and registering message handlers
• Handling support handoff messages

Guide embedding Zoom Virtual Agent in an Android WebView, a browser view inside an app. Covers communication with Java or Kotlin, URL routing, support handoff events, and embedding that accounts for the WebView lifecycle.

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

• Embedding Zoom Virtual Agent in an Android app
• Receiving JavaScript callbacks in Java or Kotlin
• Routing links from a WebView to native app handling

Design and build backend services with API scaffolding, database migrations, authentication reviews, and load testing. Generate route handlers from OpenAPI specifications, identify PostgreSQL optimization opportunities, and compare architecture choices against traffic, data sensitivity, and reliability requirements.

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

• Generating API route handlers from OpenAPI
• Investigating slow PostgreSQL queries
• Reviewing authentication and input validation

Diagnose iii invocation failures using error codes across Node, Python, Rust, and browser workers. Distinguish permission denials, timeouts, and handler failures, then choose appropriate exception handling and decide whether retrying is suitable.

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

• Diagnosing failed function calls by error code
• Deciding whether a timed-out operation should be retried
• Handling permission denials without blind retries

Build MCP servers and clients that connect AI systems to external tools and data. The skill defines validated inputs, implements tool and resource handlers, configures communication methods, and checks protocol behavior with the MCP Inspector.

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

• Expose external tools and data to AI systems through MCP
• Start an MCP project in TypeScript or Python
• Validate inputs and investigate protocol errors

Build and configure web servers with Nitro, including request handlers, caching, storage, and scheduled tasks. The skill also guides deployment to supported runtimes and platforms, plus migration from Nitro v2 to v3.

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

• Implementing server routes and caching
• Adding scheduled tasks and WebSocket connections
• Configuring deployment for supported platforms

Next.js adapter for embedding emulators directly in a Next.js app via @emulators/adapter-next. Use when the user needs to embed emulators in Next.js, set up same-origin OAuth for Vercel preview deployments, create an emulate catch-all route handler, configure Auth.js/NextAuth with embedded emulators, add persistence to embedded emulators, or wrap next.config with withEmulate. Triggers include "Next.js emulator", "adapter-next", "embedded emulator", "same-origin OAuth", "Vercel preview", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Next.js app.

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

Connects to Oxylabs remote agent browsers over the Chrome DevTools Protocol (CDP) with Playwright or Puppeteer. Managed browser environment, residential proxies, geo-targeting, persistent sessions and profiles, session recording and live VNC inspection for debugging. Use instead of WebFetch or a local browser whenever a site renders with JavaScript, serves access challenges, verification interstitials or bot-management block pages, or needs a full browser session, screenshots or PDFs. Covers connection, retries, error recovery, built-in challenge handling (the page_handler parameter, the oxylabs-page-status page state reported by the page handler, manual triggering), telling a handled challenge from a block that needs a fresh identity, and reliable access to publicly available data without manual intervention.

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

Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. This should trigger for requests such as Review or improve Micronaut @Controller REST APIs; Add validation, error handling, or align controllers with the OpenAPI contract on Micronaut HTTP layer; Design Micronaut controllers and DTO validation; Add Micronaut exception handlers and Problem Details responses; Improve pagination filtering or OpenAPI alignment in Micronaut APIs. Part of Plinth Toolkit

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

Routes heterogeneous queries to the appropriate index, tool, or answering engine before retrieval. Use when one endpoint serves multiple handlers, such as summary, vector retrieval, text-to-SQL, or tools, and query types require different paths. Covers LLM, semantic, and rule-based routers, confidence thresholds, fallbacks, and framework mappings. Do not use when one handler serves all queries or branching is fixed.

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

PowerX HTTP Handler 规则（绑定校验、统一回包、无 DB IO）。

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

Drive msfconsole across the workflow - DB-backed recon (db_nmap, auxiliary scanners), version->exploit search/check/run, multi/handler reverse shells (meterpreter-first, plain shell_reverse_tcp backup for Windows/EDR), sessions + local_exploit_suggester + post modules, and autoroute/portfwd/socks pivoting. Points to the metasploit cheatsheet for syntax. Use for "metasploit", "msfconsole", "msfvenom", "meterpreter", "multi/handler", or driving an exploit/reverse-shell through msf.

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

Use when reviewing Node.js or TypeScript server code - Express/Fastify/Nest handlers, Next.js server actions and route handlers, child_process, ORM raw queries, prototype pollution, template engines, JWT and outbound HTTP clients

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

Neo4j Visualization Library (NVL) — framework-agnostic graph rendering for the browser. Covers @neo4j-nvl/base (NVL class, nodes/relationships, Canvas vs WebGL renderer), @neo4j-nvl/interaction-handlers (ZoomInteraction, PanInteraction, DragNodeInteraction, ClickInteraction, HoverInteraction, BoxSelectInteraction, LassoInteraction, KeyboardInteraction), and @neo4j-nvl/react (InteractiveNvlWrapper, BasicNvlWrapper, StaticPictureWrapper). Use when rendering a Neo4j graph in a browser, feeding driver results through nvlResultTransformer, choosing Canvas vs WebGL, wiring node/relationship click/hover/drag handlers, or embedding NVL in React, Vite, or vanilla JS apps. Does NOT handle Cypher query authoring — use neo4j-cypher-skill. Does NOT handle driver lifecycle, sessions, or executeQuery setup — use neo4j-driver-javascript-skill. Does NOT handle GraphVisualization/Needle default embed — use @neo4j-ndl/react.

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

Design claims handling workflows with documentation and timelines. TRIGGERS - Use when user needs help with claims-handler related tasks.

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

Generates Domain Events and their handlers following DDD patterns. Implements event raising in entities, MediatR notification handlers, and the Outbox pattern for reliable event processing.

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

Create a custom script handler for an unsupported scripting language

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for GraphQL schemas, persisted queries, RPC manifests, generated clients, OpenAPI drift, hidden operations, and contract-to-handler mismatches. Use when the user asks to inspect GraphQL or RPC requests, compare client contracts to live handlers, recover hidden operations, trace generated clients, or explain how schema or contract drift produces the decisive behavior. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hydration data, compare template gating with handler enforcement, explain preview or hidden-route rendering, or connect render pipeline behavior to the decisive branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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