majiayu000/claude-skill-registry - 78ページ

api-cms-strapi

Open-source headless CMS — content type schemas, REST API, Document Service API, custom controllers, lifecycle hooks, authentication, TypeScript

原文の言語: 英語

api-codegen-runner

Use when working with api-codegen-runner

原文の言語: 英語

api-codegen-universal

Use when working with api-codegen-universal

原文の言語: 英語

api-contract-design

Design APIs using schema-first approach with OpenAPI/Swagger. Use when creating new APIs, documenting existing ones, or when frontend/backend teams need to work in parallel. Covers OpenAPI spec, validation, and code generation.

原文の言語: 韓国語

api-contract-generator

Generates OpenAPI/Swagger schemas for API endpoints. Creates comprehensive API contracts from endpoint implementations, ensuring consistency between code and documentation.

原文の言語: 英語

api-contract-sync

Use this skill when backend API contracts change and frontend types need synchronization. Triggers on: Pydantic model changes, REST endpoint updates, WebSocket message formats, or GraphQL schema modifications. Dynamically detects contract type from context.…

原文の言語: 英語

api-contract-validator

Validates API contracts for correctness, compatibility, and compliance. Tests REST APIs against OpenAPI/Swagger specifications. Detects breaking changes between versions, validates runtime responses against schemas, and ensures backward compatibility before…

原文の言語: 英語

api-contracts-and-validation

Define and validate API contracts using Zod

原文の言語: 英語

api-create-gql-query

Add a new GraphQL query endpoint with type safety, GraphORM integration, and tests

原文の言語: 英語

api-create-worker

Create a new background worker in daily-api with full type safety, infrastructure config, and tests

原文の言語: 英語

api-design

Design RESTful APIs following best practices

原文の言語: 判定不能

api-design

RESTful API and GraphQL design best practices. Auto-triggers when designing endpoints, handling HTTP methods, or structuring API responses.

原文の言語: 英語

api-design

Step-by-step guidance for API design.

原文の言語: 英語

api-design

Use when designing or modifying REST API endpoints, controller structure, route patterns, request/response DTOs. Triggers on keywords like "API endpoint", "REST", "controller", "route", "HTTP", "request body", "response".

原文の言語: 英語

api-design

"[Architecture] Use when designing or modifying REST API endpoints, controller structure, route patterns, request/response DTOs. Triggers on keywords like "API endpoint", "REST", "controller", "route", "HTTP", "request body", "response"."

原文の言語: 英語

api-design-framework

Comprehensive API design patterns for REST, GraphQL, and gRPC. Use when designing APIs, creating endpoints, adding routes, implementing pagination, rate limiting, or authentication patterns.

原文の言語: 英語

arcanea-api-design

Design APIs that developers love. RESTful principles, GraphQL patterns, versioning strategies, and the art of creating interfaces that are intuitive, consistent, and future-proof.

原文の言語: 英語

api-design

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

原文の言語: 英語

api-design-mode

Activate API design specialist mode. Expert in REST best practices, GraphQL, and OpenAPI specifications. Use when designing API contracts, endpoints, request/response formats, or API documentation.

原文の言語: 英語

api-design-patterns

RESTful API design patterns including URL structure, HTTP methods, and idempotency. Use when designing new API endpoints or reviewing API architecture. For existing projects, follow the project's established conventions instead.

原文の言語: 英語

api-design-patterns

Comprehensive REST and GraphQL API design patterns with versioning, pagination, error handling, and HATEOAS principles. Use when designing APIs, defining endpoints, or architecting service contracts requiring production-grade patterns.

原文の言語: 英語

api-design-patterns

Comprehensive REST and GraphQL API design patterns with versioning, pagination, error handling, and HATEOAS principles. Use when designing APIs, defining endpoints, or architecting service contracts requiring production-grade patterns.

原文の言語: 英語

api-design-principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

原文の言語: 英語

api-design-skill

REST/GraphQL API design patterns - resource naming, HTTP methods, error handling, pagination, versioning. Use when: design API, REST endpoints, GraphQL schema, error responses, pagination, rate limiting, API documentation.

原文の言語: 英語

api-design

REST API design best practices. Use when designing APIs, choosing status codes, or creating endpoints.

原文の言語: 英語

api-designer

Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.

原文の言語: 英語

api-designer

Conçoit des APIs REST/GraphQL avec OpenAPI spec, versioning, et documentation. Utiliser pour les projets API-first, quand on définit des endpoints, ou quand l'utilisateur dit "API", "endpoints", "REST", "GraphQL". Peut être déclenché après PRD ou Architecture.

原文の言語: フランス語

api-designer

This skill should be used when the user mentions "API design", "TypeScript API", "type-safe API", "endpoint design", "API validation", "Zod", discusses creating APIs, type safety, error handling, or API architecture. Addresses designing clean, type-safe APIs…

原文の言語: 英語

api-designer

Type-safe API design: Zod validation, Result types, SvelteKit endpoints, middleware patterns.

原文の言語: 英語

api-designer

Design RESTful or GraphQL APIs with proper conventions. Creates endpoint specifications, request/response schemas, and documentation. Use when user says 'design API', 'endpoints', 'REST', 'GraphQL', or 'API spec'.

原文の言語: 英語

api-designing

Design consistent RESTful API endpoints, request/response formats, and error handling patterns. Use when creating new API routes, designing API structure, planning request/response schemas, or establishing API conventions. Triggers on requests like "design an…

原文の言語: 英語

api-developer

When building and maintaining APIs for applications and services.

原文の言語: 英語

api-development-expert

API development expert including REST design, OpenAPI, and documentation

原文の言語: 英語

api-development

FastGPT API 开发规范。重点强调使用 zod schema 定义入参和出参,在 API 文档中声明路由信息,编写对应的 OpenAPI 文档,以及在 API 路由中使用 schema.parse 进行验证。

原文の言語: 中国語

api-development

Use when creating new API endpoints, working with async operations, implementing long-running tasks with progress tracking, adding Pydantic models, or designing request/response schemas.

原文の言語: 英語

api-development

Build REST APIs with proper error handling, status codes, request validation, response formatting, and rate limiting. Apply when creating API routes, handling errors, validating input, or designing API responses.

原文の言語: 英語

api-development

API development workflow and best practices for career_ios_backend FastAPI project. Automatically invoked when user wants to develop, test, or debug API endpoints. Trigger keywords: "API", "endpoint", "route", "FastAPI", "Swagger", "console.html", "測試 API",…

原文の言語: 英語

api-documentation-lookup

This skill should be used when the user asks to "look up Effect API", "check the Effect docs", "find Effect function signature", "what does Effect.X do", "how to use Effect.X", "Effect API reference", "fetch Effect documentation", or needs to look up specific…

原文の言語: 英語

api-docs-writer

Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions,…

原文の言語: 英語

api-documentation-question

Customer asks questions about API usage, code implementation, or technical documentation.

原文の言語: 英語