4천건 · 관련도순
Guides development of Native SDK TypeScript services for file access, network requests, and other work outside the deterministic core. Covers typed calls, pinned npm dependencies, streaming, cancellation, replay, and process or thread execution.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Windows privilege escalation paths from a standard user session to Administrator or SYSTEM. Examine service permissions, token privileges, library loading, scheduled tasks, and stored credentials, with detection indicators for defensive validation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Running an in-bundle DOCA service as a container on a BlueField (Argus, DMS, Firefly, or UROM service): kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness. Trigger on "how do I run my built service on the BlueField?", "where do I drop the pod-spec YAML?", "pod stuck in Pending / ImagePullBackOff / CrashLoopBackOff", "container Running but service isn't ready", "pod restart-loops after edit", or "DMS and Firefly together", even without naming container deployment. A DOCA-linked binary launched directly on the host or Arm belongs to doca-bare-metal-deployment. Covers smoke-before-bulk and the layered error taxonomy (pod-spec, scheduling, image pull, runtime, mount, network, version, host). Refuse and route elsewhere for per-service config schemas, DOCA install, library-API questions, external NVIDIA services (BlueMan, HBN, SNAP, Virtio-net), or full Kubernetes-cluster ops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor", "message queue", "pub/sub .NET", "dead letter queue".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge for Azure Communication Services development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building ACS calling, chat, SMS, email, Teams interop, or PSTN/Direct Routing solutions, and other Azure Communication Services related development tasks. Not for Azure Notification Hubs (use azure-notification-hubs), Azure SignalR Service (use azure-signalr-service), Azure Web PubSub (use azure-web-pubsub), Azure AI Bot Service (use azure-bot-service).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge for Azure Cloud Services development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Guest OS versions, Key Vault certs, .csdef/.cscfg configs, autoscale rules, or PowerShell automation, and other Azure Cloud Services related development tasks. Not for Azure Virtual Machines (use azure-virtual-machines), Azure App Service (use azure-app-service), Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure Functions (use azure-functions).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when querying or calling pay-per-token foundation models, or when creating, updating, listing, or querying Unity Gateway (also called Unity AI Gateway) services, including model provider services, MCP services, system.ai services, and three-part Unity Catalog service names (catalog.schema.service). Also use for managing spend budgets and usage alerts on Unity Gateway, and for migrating from legacy AI Gateway. Also use when a workload with Model Serving endpoint permissions (for example CAN_QUERY) gets PERMISSION_DENIED querying a three-part model name, since serving-endpoint access does not grant access to a Unity Gateway service. Not for configuring legacy AI Gateway on Model Serving endpoints; use databricks-model-serving for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug Fastly Compute services where code changes don't affect behavior due to multi-service routing architecture. Use when: (1) deployed changes have no effect, (2) unexpected redirects persist after code updates, (3) DNS resolves to Fastly but responses don't match deployed code, (4) `fastly service list` shows multiple related services. The root cause is often a routing/gateway service intercepting requests before they reach your content service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
HashiCorp Consul for service discovery, health checking, and service mesh. Use when the user needs to register services, perform health checks, store configuration in the KV store, or set up Connect for secure service-to-service communication.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when setting up Service Cloud Voice with Amazon Connect — provisioning the contact center, configuring phone numbers, enabling real-time transcription, and configuring After Conversation Work Time. Covers the deployable metadata behind it: CallCenter, ConversationVendorInfo (vendorType), CallCenterRoutingMap, the Voice ServiceChannel that carries ACW, ServicePresenceStatus, PresenceUserConfig, ServiceCloudVoice.settings, and the VoiceCall / VoiceCallRecording objects. Trigger keywords: Service Cloud Voice, Amazon Connect, contact center, softphone, call transcription, After Conversation Work, ACW, wrap-up time, VoiceCall, CallCenter metadata, vendorType, telephony provider. NOT for Omni-Channel routing setup — use admin/omni-channel-routing-setup. NOT for Open CTI softphone adapters — use apex/cti-adapter-development. NOT for Sales Dialer (Voice.settings) — that is a different product.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when designing the UX and content strategy for a Salesforce-powered self-service portal or help center — pre-deflection article surfacing, Help Center search UX, friction-calibrated case submission forms, community peer support layers, and deflection measurement. Trigger keywords: design self-service portal, case deflection strategy, help center UX design, reduce support volume with self-service, knowledge base search experience. NOT for picking which contact reasons to deflect and through which channel — use architect/case-deflection-strategy. NOT for building the Experience Cloud site itself — use admin/experience-cloud-site-setup. More trigger keywords: article visibility matrix IsVisibleInCsp IsVisibleInPkb, which articles show in the customer portal, case visibility for portal users, CaseComment IsPublished customer visible comment, self-registration profile and account for a portal, Help Center template does not support login, deflection metrics SOQL KnowledgeArticleViewStat, self-service journey map, moderation policy for a support community.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configuring or troubleshooting the Nonprofit Success Pack Program Management Module (PMM) - program delivery, cohort setup, service scheduling, service delivery recording, and attendance tracking for beneficiaries. Trigger keywords: program management module, PMM, Program__c, ProgramEngagement__c, ServiceDelivery__c, cohort setup, bulk service delivery, service schedule, service participant. NOT for designing which outcomes and indicators to measure - use admin/program-outcome-tracking-design. NOT for NPSP donor, household and giving-rollup data - use data/nonprofit-data-architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
HTCMC PCHSystem 专用 skill——为各子服务目录生成与更新「分布式 CLAUDE.md」（提炼该服务的雷点、关键要素、文档索引）。当新建子服务、子服务架构发生变更、或需要补齐/更新某个服务的 CLAUDE.md 时使用。传入服务名（mcdr-plugin / user-service / project-service / scoring-service / title-service / wiki-service / alert-service / frontend），本 skill 自动读取对应架构文档，按统一模板生成或增量更新该服务目录下的 CLAUDE.md。在 PCHSystem 项目内，只要用户提到「子服务 CLAUDE.md」「为某服务生成/更新 CLAUDE.md」「补齐服务雷点」「服务记忆文件」，或正在新增/改动某个服务目录，就应使用本 skill——禁止手写子服务 CLAUDE.md。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts one service catalogue entry (description, scope in and out, owners and support groups, service levels exactly as provided, request path, dependencies, charging, lifecycle) from the service team's notes, questionnaire answers or existing documents, with UNKNOWN and a question list for every field the inputs do not cover. Never invents a service level, owner or price. Use when the user asks to "write the catalogue entry for this service", "turn these questionnaire answers into a service description", "tidy this request catalogue item" or "check this draft entry for empty fields". Do not use for a how-to or known-error article, use knowledge-article-drafter instead; for operating procedures, use runbook-drafter. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Locate CCSPlayerController_InventoryServices::m_pInventory in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayerController_InventoryServices::m_pInventory" (symbol CCSPlayerController_InventoryServices_m_pInventory). This is a STRUCT MEMBER OFFSET (schema netvar), not a function. Resolve the CCSPlayerController_InventoryServices class layout via the schema/network system; m_pInventory is an 8-byte pointer member early in the class (must stay 8-aligned). Cross-check: functions of the class dereference this->m_pInventory shortly after entry. Trigger: CCSPlayerController_InventoryServices_m_pInventory, CCSPlayerController_InventoryServices::m_pInventory
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Locate CCSPlayer_MovementServices::Pawn in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSPlayer_MovementServices::Pawn" (symbol CCSPlayer_MovementServices_Pawn). This is a STRUCT MEMBER OFFSET (schema netvar), not a function. Resolve the CCSPlayer_MovementServices class layout via the schema/network system; the member must satisfy natural alignment. Cross-check with functions that dereference the member. Do not switch output schema: emit the structmember fields below even if the class turns out to be polymorphic - a func_*/vfunc_* payload for this symbol is rejected by canonical_symbol_yaml_bytes. Trigger: CCSPlayer_MovementServices_Pawn, CCSPlayer_MovementServices::Pawn
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Locate CCSPlayer_ItemServices::SetWearables in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayer_ItemServices::SetWearables" (symbol CCSPlayer_ItemServices_SetWearables). VIRTUAL function, but WeaponPaints consumes it as a byte signature. Resolve the CCSPlayer_ItemServices vtable via RTTI to locate the slot, then generate a function-head byte signature of the resolved function. The body copies wearable item handles into the pawn's wearable array (m_Item wearables netvar array) and marks state changed. Trigger: CCSPlayer_ItemServices_SetWearables, CCSPlayer_ItemServices::SetWearables
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Locate CCSPlayer_WeaponServices::DropWeapon in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayer_WeaponServices::DropWeapon" (symbol CCSPlayer_WeaponServices_DropWeapon). This is a VIRTUAL function — emit the vtable slot, NOT a byte signature. Resolve the CCSPlayer_WeaponServices vtable via RTTI and identify the DropWeapon slot: the body takes a CBasePlayerWeapon handle/pointer, detaches it from the player, spawns the dropped weapon entity and transfers ownership. Verify by xrefs from weapon-drop commands (!!drop) and pickup logic. vtable slots commonly differ between platforms — never assume identical indices. Trigger: CCSPlayer_WeaponServices_DropWeapon, CCSPlayer_WeaponServices::DropWeapon
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consumer-Driven Contract Testing (CDC) using Pact framework and OpenAPI-based contract validation. Covers microservice-to-microservice contract verification, provider contract testing, consumer contract testing, contract publishing pipelines, and contract breaking-change detection. USE WHEN: designing microservice APIs, establishing service boundaries, verifying service-to-service contract compatibility, integrating with Pact framework, preventing contract-breaking changes, or setting up a contract testing pipeline in CI/CD. Triggers on "contract test", "Pact", "consumer- driven contract", "CDC", "service contract", "API contract", "breaking change".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stripe Projects로 프로젝트에 데이터베이스와 SMS 등 외부 서비스를 준비합니다. 인증 정보를 `.env`에 동기화하고 키 갱신, 요금제 변경과 서비스 제거를 관리합니다.
MCP로 Claude Code 플러그인에 외부 서비스를 연결하도록 안내합니다. 연결 방식과 인증, 도구 권한을 설정하고 연결 및 도구 호출 동작을 확인합니다.
Implement shared authentication for Azure Communication Services in Java, including automatic renewal of access tokens, the credentials used to access services. It also guides handling identifiers for ACS users, phone numbers, and Microsoft Teams users.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.