'service' 검색 결과

Selects, investigates, and compares AWS object, file, and block storage services, and answers cost, performance, configuration, security, and troubleshooting questions about storage services. Applies when a user asks where to store or archive data based on their usage patterns; which storage service to choose or how two compare; how to migrate data from on-premises or between AWS services; how to protect, replicate, or recover data; how to optimize storage costs; where to deploy shared NFS, SMB, or POSIX file systems; where to store vector embeddings or tabular data; what storage backs enterprise file shares, self-managed databases on EC2, VMware, or stateful containers; or asks what an AWS storage service can do or how it works. Relevant for storage needs for workloads such as AI/ML, analytics, EDA, HPC, media, genomics, or financial trading. Not applicable for SQL query engines (Athena, Spark, Redshift, EMR), ETL (Glue), streaming (Kafka, MSK, Kinesis), or managed database services (RDS, Aurora, DynamoDB).

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

Guides general use of AWS messaging and streaming services. Covers Amazon SQS, Amazon SNS, Amazon EventBridge, Amazon MQ, Amazon Kinesis Data Streams, Amazon Data Firehose, Amazon Managed Service for Apache Flink, and Amazon Managed Streaming for Apache Kafka (MSK). Use when reasoning about messaging and streaming patterns. Also identifies which AWS service owns each customer communication channel: email (Amazon SES), and WhatsApp, SMS, MMS, RCS, voice and mobile push (the AWS End User Messaging family of services). Routes the request to the specialized skill for that channel. Defers to the channel's specialized skill when the user already named a specific channel. In general, use specific skills or documentation searches for detailed service-specific questions. Do NOT use for MSK or Managed Service for Apache Flink questions, prefer specific skills. Does not configure customer communication channels; defers to specific skills.

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

Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux. WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare.

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

Expert knowledge for Azure Service Connector development including troubleshooting, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when wiring Azure compute to Redis, databases, storage, messaging, AI services, or third‑party endpoints, and other Azure Service Connector related development tasks. Not for Azure API Management (use azure-api-management), Azure Connector Namespace (use azure-connector-namespace), Azure Logic Apps (use azure-logic-apps), Azure Service Bus (use azure-service-bus).

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

Expert knowledge for Azure Kubernetes Service (AKS) development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when running GPU/AI or PCI apps, using Fleet, KEDA, service meshes, or integrating AKS with Key Vault, and other Azure Kubernetes Service (AKS) related development tasks. Not for Azure Container Apps (use azure-container-apps), Azure Container Instances (use azure-container-instances), Azure Red Hat OpenShift (use azure-redhat-openshift), Azure Service Fabric (use azure-service-fabric).

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

Expert knowledge for Azure AI Bot Service development including troubleshooting, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Direct Line 3.0, configuring Teams/Web Chat channels, setting App Service bots, CI/CD, or App Insights, and other Azure AI Bot Service related development tasks. Not for Azure Health Bot (use azure-health-bot), Azure Functions (use azure-functions), Azure App Service (use azure-app-service).

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

Build long-running .NET background services with `BackgroundService`, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

中国网站备案 与 互联网内容合规 (含 ICP 备案 主体+网站 / 公安备案 / ICP 经营许可证 增值电信 / 域名实名认证 / APP 备案 2024 工信部新规 / 等级保护测评 网安 / 算法推荐 + 深度合成 + 生成式 AI 备案 网信办 / 数据出境 + 个保法 + 数安法 合规联动 / 变更注销转移跨省迁移 — 不含 通用法律咨询 / 海外域名注册 / 网络营销 SEO / 翻墙 VPN) (China ICP filing & internet content compliance — the full regulatory life-cycle for any website / app / mini-program / IT service that publishes content or runs commercial services targeting mainland-China users; covers (a) 主体备案 + 网站备案 (non-commercial ICP record on beian.miit.gov.cn 经接入商 提交), (b) 域名实名认证 (CNNIC 一级域名 / 注册商核验), (c) 公安备案 (网安部门 30 日内补办), (d) ICP经营许可证 (有偿经营 / 增值电信业务 — 申请门槛极高), (e) APP 备案 (2024-03 工信部令), (f) 等级保护测评 (公安部 GB/T 22239), (g) 算法推荐 / 深度合成 / 生成式 AI 备案 (网信办专项), (h) 数据出境 + 个保法 + 数安法 合规联动, (i) 变更 / 注销 / 转移 / 跨省迁移 工作流; NOT 通用法律咨询, NOT 海外域名注册技术, NOT 网络营销 SEO, NOT 翻墙 / VPN 相关.) Master OS — automated mastery of China ICP filing & internet content compliance — the full regulatory life-cycle for any website / app / mini-program / IT service that publishes content or runs commercial services targeting mainland-China users; covers (a) 主体备案 + 网站备案 (non-commercial ICP record on beian.miit.gov.cn 经接入商 提交), (b) 域名实名认证 (CNNIC 一级域名 / 注册商核验), (c) 公安备案 (网安部门 30 日内补办), (d) ICP经营许可证 (有偿经营 / 增值电信业务 — 申请门槛极高), (e) APP 备案 (2024-03 工信部令), (f) 等级保护测评 (公安部 GB/T 22239), (g) 算法推荐 / 深度合成 / 生成式 AI 备案 (网信办专项), (h) 数据出境 + 个保法 + 数安法 合规联动, (i) 变更 / 注销 / 转移 / 跨省迁移 工作流; NOT 通用法律咨询, NOT 海外域名注册技术, NOT 网络营销 SEO, NOT 翻墙 / VPN 相关.: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on China ICP filing & internet content compliance — the full regulatory life-cycle for any website / app / mini-program / IT service that publishes content or runs commercial services targeting mainland-China users; covers (a) 主体备案 + 网站备案 (non-commercial ICP record on beian.miit.gov.cn 经接入商 提交), (b) 域名实名认证 (CNNIC 一级域名 / 注册商核验), (c) 公安备案 (网安部门 30 日内补办), (d) ICP经营许可证 (有偿经营 / 增值电信业务 — 申请门槛极高), (e) APP 备案 (2024-03 工信部令), (f) 等级保护测评 (公安部 GB/T 22239), (g) 算法推荐 / 深度合成 / 生成式 AI 备案 (网信办专项), (h) 数据出境 + 个保法 + 数安法 合规联动, (i) 变更 / 注销 / 转移 / 跨省迁移 工作流; NOT 通用法律咨询, NOT 海外域名注册技术, NOT 网络营销 SEO, NOT 翻墙 / VPN 相关. problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「ICP备案」「icp备案」「icp filing」「icp license」「中国备案」

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

Configure Messaging for In-App and Web (MIAW) channels in Service Cloud: Messaging Channel, Embedded Service Deployment, CORS/CSP Trusted Sites, pre-chat fields, session routing by Queue or Omni-Channel Flow, Status-Based capacity, Live Agent migration. Trigger keywords: MessagingChannel, EmbeddedServiceConfig, messagingChannelType, EmbeddedMessaging, sessionHandlerQueue, sessionHandlerFlow, embeddedConfig, automatedResponses, CorsWhitelistOrigin, CspTrustedSite, BrandingSet, MessagingSession, MessagingEndUser, enhanced chat, embedded messaging, chat widget, pre-chat form, auto-response. NOT for an Agentforce agent in the chat window - use agentforce/agent-channel-deployment. NOT for Omni-Channel enablement, Service Channels or skills-based routing - use admin/omni-channel-routing-setup.

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

Operational setup guide for Salesforce Energy and Utilities Cloud: license activation, permission sets, industry-specific object configuration (ServicePoint, Meter, MeterReading, Consumption, ServiceAccount, ServiceContract, RatePlan), CIS/billing system integration, and service order management. NOT for generic admin setup, NOT for reading or querying the E&U data model schema (use architect/industries-data-model for that).

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

Configuring Salesforce Omni-Channel routing from scratch or updating existing routing: enabling Omni-Channel, creating Service Channels, configuring Routing Configurations (queue-based and skills-based), setting up Presence Statuses and Presence Configurations, assigning skills to Service Resources, and defining Skills-Based Routing Rules. Trigger keywords: Omni-Channel setup, routing configuration, queue-based routing, skills-based routing, presence status, service channel, routing rules. NOT for agent capacity units and channel weighting — use architect/omni-channel-capacity-model. NOT for Apex routing via PendingServiceRouting — use apex/omni-channel-custom-routing.

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

Use this skill to configure Field Service Lightning service territories — including territory types, operating hours, time slots, territory hierarchy, member types, and polygon boundaries. NOT for Enterprise Territory Management (Territory2) in Sales Cloud — use admin/enterprise-territory-management. NOT for bulk-loading territory polygons or members — use data/fsl-territory-data-setup.

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

Decompose systems into microservices and apply canonical distributed-systems patterns. Use this skill whenever the user wants to split a monolith into services, design service boundaries, choose between microservices and a modular monolith, implement sagas or the outbox pattern, set up CQRS or event sourcing, configure an API gateway or BFF, add resilience (circuit breakers, retries, timeouts), or implement distributed tracing with OpenTelemetry. Also trigger for distributed transactions, service discovery, event-driven architecture, contract testing with Pact, canary releases, and idempotent consumers.

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

Architect scalable backend services using layered architecture, dependency injection, middleware patterns, service classes, and separation of concerns. Use when building API services, implementing business logic layers, creating service classes, setting up middleware chains, implementing dependency injection, designing controller-service-repository patterns, handling cross-cutting concerns, creating domain models, implementing CQRS patterns, or establishing backend architecture standards.

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

Locate CCSPlayer_WeaponServices::GetSlot 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_WeaponServices::GetSlot" (symbol CCSPlayer_WeaponServices_Weapon_GetSlot). This is a non-virtual function - emit a byte signature (func_sig), not an offset. Locate it via cross-references, distinctive constants/strings in its body, or callers of related symbols; verify by decompilation before committing to a candidate. Trigger: CCSPlayer_WeaponServices_Weapon_GetSlot, CCSPlayer_WeaponServices::GetSlot

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

Search and browse the x402 bazaar marketplace for paid API services. Use when you or the user want to find available services, see what's available, discover APIs, or need an external service to accomplish a task. Also use as a fallback when no other skill clearly matches — search the bazaar to see if a paid service exists. Covers "what can I do?", "find me an API for...", "what services are available?", "search for...", "browse the bazaar".

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

여러 머신으로 구성된 Uncloud에서 서비스를 배포하고 관리합니다. uc CLI로 공개 포트, Caddy 설정, 복제본 수 조정, 로그 확인과 볼륨 관리를 진행합니다.

• Compose 파일로 서비스 배포
• 웹 앱을 HTTPS로 공개
• NAS나 라우터로 연결되는 경로 설정

Java의 Quarkus 서비스 설계와 검토를 지원합니다. REST API 구성, Panache 데이터 접근, Camel 메시지 연계와 비동기 처리의 구현 패턴을 제공합니다.

• REST API의 책임 분리
• Camel과 RabbitMQ 연계
• Panache 저장 처리 검토

Ruby on Rails 앱의 구현과 검토에서 업무 처리, 검색, 폼의 책임을 정리합니다. 불필요한 데이터 조회를 줄이고 백그라운드 작업과 화면 구성 요소 설계도 돕습니다.

• 큰 controller의 업무 처리를 분리합니다
• 여러 모델을 갱신하는 폼을 설계합니다
• 중복 검색과 데이터 조회를 검토합니다

Paperclip의 격리된 개발 환경을 관리 서비스로 시작하고 복구합니다. 데이터베이스 복제, 로그인, 운영 화면의 상태와 포트 점유 프로세스의 소속을 확인합니다.

• 관리되는 개발 환경 시작 및 재시작
• 초기 설정·로그인·복제 데이터 문제 복구
• 작업 환경 사이의 포트 충돌 해결

Design or improve what you sell by reviewing customer value, deliverables, bonuses, guarantees, deadlines, naming, and payment terms. Identify weak parts of a service, course, or coaching offer and draft specific changes to test.

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

• Package consulting services for sale
• Review course bonuses and guarantees
• Diagnose why an offer is not converting

Retrieve and combine protein annotations, biological pathways, and chemical identifiers from services such as UniProt, KEGG, and UniChem using Python. Supports cross-database lookups and batch identifier conversion while preserving multiple matches and failed requests.

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

• Collect protein sequences and functional annotations
• Retrieve pathway information for genes
• Match compound identifiers across databases

Build server-side calling workflows in Java with Azure Communication Services. Implement automated phone menus, incoming and outgoing calls, transfers, recording, spoken prompts, and recognition of speech or keypad input, with examples for handling call events.

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

• Building automated phone menus in Java
• Routing incoming calls to another number
• Adding spoken prompts and keypad or speech input

Design traffic controls for AI inference services using Istio configuration examples. Covers mutual authentication, model version routing, gradual releases, retry limits, failure containment, and monitoring, with guidance for validating changes on the target cluster.

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

• Secure communication between inference services
• Gradually route requests to a new model version
• Review retries and failure containment for GPU services