266건 · 관련도순
Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when "hubspot, hubspot api, hubspot crm, hubspot integration, contacts api, hubspot, crm, marketing, sales, api" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user syncUse when "adding authentication, clerk auth, user authentication, sign in, sign up, user management, multi-tenancy, organizations, sso, single sign-on, clerk, authentication, auth, user-management, multi-tenancy, organizations, sso, oauth" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AgentPhone workflow skill. Use this skill when the user needs Build AI phone agents with AgentPhone API. Use when the user wants to make phone calls, send/receive SMS, manage phone numbers, create voice agents, set up webhooks, or check usage — anything related to telephony, phone numbers, or voice AI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AgentPhone workflow skill. Use this skill when the user needs Build AI phone agents with AgentPhone API. Use when the user wants to make phone calls, send/receive SMS, manage phone numbers, create voice agents, set up webhooks, or check usage — anything related to telephony, phone numbers, or voice AI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AgentMail — Email for AI Agents workflow skill. Use this skill when the user needs Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AgentMail — Email for AI Agents workflow skill. Use this skill when the user needs Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the diff adds or changes a gRPC service or interceptor, a GraphQL resolver or subscription, a protobuf/Thrift schema, a queue or pub/sub producer or consumer, an event handler or an inbound webhook - peer identity vs claimed principal, interceptor gaps, per-item and stream authorization, webhook signatures, untrusted producers, enum defaults, replay, duplicate delivery and ordering
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the server side of the diff fetches, renders, redirects to or validates a URL that input can influence - webhooks, link previews, import-from-URL, PDF renderers, OAuth/JWKS discovery, allowlist and blocklist checks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design REST/GraphQL APIs with OpenAPI 3.1, error handling, pagination, rate limiting, webhooks, and idempotency. Use when user asks to design an API, create endpoints, define REST/GraphQL schema, or generate OpenAPI spec. Do NOT use for database schema design, frontend API integration, or non-HTTP protocols (gRPC, WebSocket, MQTT).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tests API contracts for REST, GraphQL, gRPC, AsyncAPI, and webhooks. Use when adding schema validation or breaking-change gates (Pact, can-i-deploy, oasdiff, buf); not API design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clerk Billing for subscription management - render Clerk's PricingTable and in-app checkout drawer, configure subscription plans, seat-limit plans for B2B, feature entitlements with has(), and billing webhooks. Use for SaaS monetization, plan gating, checkout flows, trials, invoicing, and subscription lifecycle management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Shopify apps, extensions, themes with Shopify CLI. Use for GraphQL/REST APIs, Polaris UI, Liquid templates, checkout customization, webhooks, billing integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run, diagnose, or manually test the private Stacktape Console locally, especially when local API/UI behavior must use the shared dev RDS data, Cognito users, AWS services, OAuth callbacks, or provider webhooks. Use for Console dev-mode setup, deciding between UI-only and full mode, shared-dev migrations, and GitHub/GitLab/Bitbucket end-to-end testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for headless WordPress architecture — WPGraphQL, ACF Pro, Faust.js, Next.js/Astro frontend, webhooks, and caching / Panduan ahli arsitektur WordPress headless.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement and audit SaaS billing systems, subscription state machines, secure webhooks, and local database synchronization / Implementasi dan audit sistem billing SaaS, state machine langganan, webhook aman, dan sinkronisasi database lokal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for integrating payment gateways (Stripe, PayPal, Xendit, Midtrans, DOKU SNAP BI) and secure webhooks into SaaS platforms / Panduan ahli integrasi payment gateway dan webhook aman.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply Stripe API integration patterns: webhooks, idempotency keys, and subscription handling. Use when integrating Stripe payments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure Vapi server URLs and webhooks to receive real-time call events, transcripts, tool calls, and end-of-call reports. Use when setting up webhook endpoints, building tool servers, or integrating Vapi events into your application.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, create, run, monitor, and maintain Vapi Simulations for assistants and squads. Use for turning plain-language requirements into a coverage plan, simulation personalities, scenarios, structured-output success criteria, simulations, suites, extending an existing suite, chat or voice runs, tool mocks, target variables, lifecycle webhooks, regression coverage, launch readiness, CI quality gates, run-result analysis, and simulation API validation errors. Do not use for fixed-turn mock-conversation Evals unless the user is deciding between Evals and Simulations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, schedule, duplicate, inspect, cancel, archive, and troubleshoot Vapi outbound Campaigns. Use for persistent multi-contact calling, CSV or API contact personalization, campaign concurrency, campaign webhooks, pre-dial eligibility, contact outcomes, or rerunning an audience. Do not use for a single call or a simple one-off /call batch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create one-off outbound phone calls, web calls, scheduled calls, and simple batch calls using the Vapi API. Use when making or testing individual calls or initiating a bounded /call request programmatically. Use create-campaign for a persistent multi-contact Campaign with lifecycle, reporting, cancellation, duplication, or campaign webhooks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kubernetes API analysis, service-account trust, RBAC edges, admission and controller behavior, cluster secrets, workload mutation, and namespace-scoped drift. Use when the user asks to inspect kube API permissions, service-account tokens, RoleBinding or ClusterRoleBinding edges, admission webhooks, controller-created pods, secret exposure, or why live workloads differ from manifests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.