405건 · 관련도순
API Design Principles workflow skill. Use this skill when the user needs Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API Design Principles workflow skill. Use this skill when the user needs Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize GraphQL queries and resolvers for performance. Use when a mid-level developer needs to reduce N+1 or payload size.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and status updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract, suggest, and sync tags and categories for blog posts across all major CMS platforms. Supports WordPress REST API, Shopify GraphQL, Ghost Content API, Strapi REST/GraphQL, and Sanity GROQ. Generates tag suggestions from content analysis (keyword frequency, heading extraction, semantic grouping), enforces minimum post-count thresholds to prevent thin tag archives, and syncs taxonomy via authenticated API calls. Use when user says "tags", "categories", "taxonomy", "tag suggestions", "sync tags", "WordPress tags", "Shopify tags".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with constraints and indexes, or assessing an existing model against graph modeling best practices. Does NOT handle Cypher query authoring — use neo4j-cypher-skill. Does NOT handle Spring Data Neo4j entity mapping — use neo4j-spring-data-skill. Does NOT handle GraphQL type definitions — use neo4j-graphql-skill. Does NOT handle data import — use neo4j-import-skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for designing robust APIs: REST best practices, GraphQL, gRPC, tRPC, OpenAPI/Swagger, API versioning, rate limiting, and contract-first design / Panduan ahli untuk merancang API yang kuat: praktik terbaik REST, GraphQL, gRPC, tRPC, OpenAPI/Swagger, versioning API, rate limiting, dan desain contract-first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive a GitHub Copilot (or any bot reviewer) pull-request review to a clean pass without babysitting it: fix each finding in its own commit, reply to the review thread with the fix sha, resolve the thread, re-request the bot, and poll for the async re-review. Covers the thread node-id (PRRT_...) vs comment databaseId distinction, the resolveReviewThread GraphQL mutation, the copilot-pull-request-reviewer[bot] slug, and how to read the bot's verdict (COMMENTED plus a "human review recommended" banner is not a blocking finding). Use when Copilot has left review comments on your PR, when bot review threads must be closed out with an auditable fix-reply-resolve trail before merge, or when you need to verify that a re-review actually landed on the new HEAD rather than the old one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GraphQL expert including schema design, Apollo Client/Server, and caching
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API security testing and validation for REST/GraphQL/gRPC endpoints, contract testing, load testing, fuzzing, and Postman/Bruno/Hurl workflows
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API security automation skill for REST, GraphQL, gRPC, and WebSocket APIs. Covers OpenAPI/AsyncAPI ingestion, authenticated fuzzing, OWASP API Top 10 (BOLA, BFLA, mass assignment, SSRF), schema diffing, GraphQL introspection abuse, JWT and OAuth misuse, rate-limit and replay testing. Use to automate API assessments with safe, scoped, evidence-backed findings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prismatic API access patterns and GraphQL reference. Covers the two-tier access hierarchy (MCP tools → Prism CLI), CLI usage rules, GraphQL query patterns, pagination, authentication, and managing platform resources programmatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apollo Client GraphQL patterns — normalized cache and type policies, queries, mutations with optimistic updates, pagination, fragments, subscriptions, and Suspense hooks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
URQL GraphQL client patterns — the exchange pipeline, document and normalized caching, queries, mutations, subscriptions, and authentication
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GraphQL API server with Apollo Server — schema, resolvers, context, error handling, data sources, plugins
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GraphQL server for Fastify with Mercurius — loaders, subscriptions, federation, JIT compilation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GraphQL Yoga v5 server, Envelop plugins, subscriptions, error masking
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architect data fetching with TanStack Query v5, SWR, optimistic updates, prefetching, and cache invalidation strategies. Activate on: React Query, SWR, optimistic updates, cache invalidation, prefetching, stale-while-revalidate, infinite queries. NOT for: REST API design (use api-architect), database queries (use database skills), GraphQL schema (use graphql-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and review durable REST, GraphQL, RPC, or event-facing API contracts. Use for public or shared API contracts, endpoint/schema consistency, compatibility, pagination, error semantics, and API documentation. Discovers existing consumers and conventions before recommending a style.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
REST/GraphQL API testing with automated validation — test endpoints, validate responses, check status codes, and ensure API contracts
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debugs REST and GraphQL APIs: unexpected status codes or bodies, auth failures (401/403, OAuth, API keys), schema mismatches, rate limits, pagination, and webhooks. Use when a request works in Postman but not in code, an integration test fails, or a callback misbehaves; not for UI rendering or DB tuning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.