API Docs

Type-safe API development with Hono framework. Covers route chaining for type inference, factory patterns, Zod OpenAPI integration, error handling, RPC client, and testing patterns. Use when building APIs with Hono, using hc client, or when Hono, RPC, OpenAPI, or --hono flag mentioned.

REST API design patterns for SpecFlux. Use when creating new API endpoints, designing request/response schemas, implementing pagination, or updating OpenAPI specifications. Follows Domain-Driven Design with specs organized by domain.

A tool for generating fully typed API clients from OpenAPI schemas. It offers a fetch-compatible API, auto-generated types without generics, and integrates with major build tools like Vite, Next.js, and Webpack.

Design and manage API contracts before implementation using OpenAPI and AsyncAPI specifications for contract-first development

Author and validate OpenAPI 3.1 specifications for REST API design, following API-first and contract-first development practices

Expert API architect specializing in RESTful API design, GraphQL, gRPC, and API security. Deep expertise in OpenAPI 3.1, authentication patterns (OAuth2, JWT), rate limiting, pagination, and OWASP API Security Top 10. Use when designing scalable APIs, implementing API gateways, or securing API endpoints.

FastAPI web framework patterns. Triggers on: fastapi, api endpoint, dependency injection, pydantic model, openapi, swagger, starlette, async api, rest api, uvicorn.

Contract-first REST API design with OpenAPI 3.1 specification

Generates OpenAPI/Swagger/GraphQL documentation and SDKs from code

Generate API specification documentation from codebase analysis. Detects REST endpoints, function signatures, type definitions, and schemas. Triggers: API specification, endpoints, REST API, type definitions, OpenAPI, Swagger, API documentation.

コードベース分析からAPI仕様ドキュメントを生成。 RESTエンドポイント、関数シグネチャ、型定義、スキーマを検出。 トリガー: API specification, endpoints, REST API, type definitions, OpenAPI, Swagger, API documentation.

Generate and validate Python clients from OpenAPI specs. Use for generation, validation, or troubleshooting.

Use this skill when creating, modifying, or reviewing API endpoints and routes. This includes SDK routes (/v1/*), Dashboard routes (/api/v1/*), request/response structures, input validation, OpenAPI documentation, or API-related middleware.

This skill automates API endpoint testing, including request generation, validation, and comprehensive test coverage for REST and GraphQL APIs. It is used when the user requests API testing, contract testing, or validation against OpenAPI specifications. The skill analyzes API endpoints and generates test suites covering CRUD operations, authentication flows, and security aspects. It also validates response status codes, headers, and body structure. Use this skill when the user mentions "API testing", "REST API tests", "GraphQL API tests", "contract tests", or "OpenAPI validation".

API 文档生成工具。当用户需要生成 API 接口文档、维护接口规范、或进行前后端接口对接时使用。支持从前端或后端代码生成标准化的 API 文档。

Swagger UI を用いた OpenAPI ドキュメントの公開・統合を支援するスキル。静的HTML/React/Next.js/サーバー埋め込みの構成を整理し、安全なAPI Explorerを構築する。Anchors:• OpenAPI Specification / 適用: API仕様互換 / 目的: 定義の一貫性確保• Swagger UI Documentation / 適用: UI構成 / 目的: 設定項目の正確な適用• OWASP ASVS / 適用: 公開・認証設計 / 目的: セキュリティ要件の確認Trigger:Use when embedding or publishing Swagger UI, configuring OpenAPI docs, or securing API explorer access.swagger ui, openapi docs, api explorer, swagger config, authentication

API仕様に整合したリクエスト/レスポンス例とエラーレスポンス例を作成するスキル。cURLとSDKサンプルを含め、実行可能で説明的な例示を短時間で整備する。Anchors:• OpenAPI Specification / 適用: 例示とスキーマ整合 / 目的: 仕様一致• RFC 7807 Problem Details / 適用: エラーレスポンス設計 / 目的: 形式統一• API Design Patterns (J.J. Geewax) / 適用: 例示設計 / 目的: 利用者理解の促進Trigger:Use when creating API request/response examples, cURL samples, SDK snippets, and error case documentation aligned with the API specification.request response examples, cURL, SDK examples, error responses, OpenAPI

This skill validates API contracts using consumer-driven testing and OpenAPI validation. It leverages Pact for consumer-driven contract testing, ensuring that API providers adhere to the expectations of their consumers. It also validates APIs against OpenAPI specifications to guarantee compliance and identify breaking changes. Use this skill when the user asks to generate contract tests, validate API responses, check backward compatibility, or validate requests/responses using the terms "contract-test", "ct", "Pact", "OpenAPI validation", or "consumer-driven contract testing".

Domain specialist for API design, development, and best practices. Scope: RESTful API design, GraphQL, API documentation, authentication, authorization, rate limiting, CORS, error handling, pagination, filtering, HATEOAS, API testing, API security. Excludes: database design, business logic, infrastructure, frontend, security beyond API. Triggers: "API", "REST", "GraphQL", "endpoint", "OpenAPI", "Swagger", "CORS".

OpenAPI、Swagger、RESTful APIドキュメンテーションのベストプラクティスを提供する専門スキル。Anchors:• 『RESTful Web APIs』（Leonard Richardson）/ 適用: REST APIドキュメンテーション / 目的: リソース設計とHTTP操作の標準化Trigger:OpenAPI/Swagger定義設計時、APIエンドポイント仕様書作成時、REST APIドキュメント整備時、認証仕様文書化時、エラーレスポンス標準化時、ドキュメントレビュー時に使用