API Development
228 skills in Development > API Development
github-api-integration
GitHub APIをGitHub Actions内で活用するための統合スキル。REST APIとGraphQL APIの両方を使用して、Issue、Pull Request、リリース、ワークフローなどの自動化を実現。Anchors:• GitHub REST API / 適用: Issue、PR、リポジトリ操作 / 目的: 標準的なCRUD操作• GitHub GraphQL API / 適用: 複雑なデータ取得 / 目的: 効率的なバッチ処理• RESTful Web APIs (Leonard Richardson) / 適用: API設計原則 / 目的: 適切なリソース設計Trigger:Use when integrating GitHub API calls in GitHub Actions, automating Issue and PR operations, generating release notes, managing repositories programmatically, or handling API authentication and rate limiting.github api, rest api, graphql, gh cli, automation, issue, pull request, release
api-documentation-best-practices
OpenAPI、Swagger、RESTful APIドキュメンテーションのベストプラクティスを提供する専門スキル。Anchors:• 『RESTful Web APIs』(Leonard Richardson)/ 適用: REST APIドキュメンテーション / 目的: リソース設計とHTTP操作の標準化Trigger:OpenAPI/Swagger定義設計時、APIエンドポイント仕様書作成時、REST APIドキュメント整備時、認証仕様文書化時、エラーレスポンス標準化時、ドキュメントレビュー時に使用
api-engineering
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".
automating-api-testing
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".
performance-optimization
Use when analyzing and improving performance for database queries, API endpoints, or frontend rendering.
api-contract-normalizer
Unifies API response patterns across endpoints including pagination format, error structure, status codes, response envelopes, and versioning strategy. Provides contract documentation, shared TypeScript types, middleware utilities, and migration plan. Use when standardizing "API contracts", "response formats", "API conventions", or "API consistency".
rate-limiting
Rate Limitingとクォータ管理のベストプラクティスを提供するスキル。 サーバー側のAPI保護とクライアント側の429対応の両方をカバーし、 Token Bucket、Sliding Window等のアルゴリズム選定から実装までを支援。 Anchors: • 『Designing Data-Intensive Applications』(Kleppmann)/ 適用: 分散システムのRate Limiting / 目的: スケーラブルな設計 • 『API Design Patterns』(Geewax)/ 適用: API保護 / 目的: RESTful APIのベストプラクティス • RFC 6585 / 適用: 429 Too Many Requests / 目的: 標準準拠のレスポンス設計 Trigger: Use when designing API rate limiting, implementing DoS protection, handling external API rate limits, or managing quota systems. rate limiting, rate limiter, throttling, 429, token bucket, sliding window, quota, api protection
tracking-application-response-times
This skill enables Claude to track and optimize application response times. It uses the response-time-tracker plugin to monitor API endpoints, database queries, external service calls, frontend rendering, and background job execution. The plugin calculates P50, P95, and P99 percentiles, average and maximum response times. Use this skill when you need to identify performance bottlenecks, monitor SLOs, or receive alerts about performance degradation. Trigger this skill with phrases like "track response times", "optimize latency", or "monitor application performance".
automating-api-testing
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".
http-best-practices
HTTPプロトコルの仕様に基づき、RESTful APIおよびWebサービス実装における通信設計を提供。ステータスコード、ヘッダー、キャッシュ、冪等性設計を網羅。Anchors:• HTTP/2 in Action (Barry Pollard) / 適用: プロトコル仕様・パフォーマンス / 目的: 効率的なHTTP通信• RESTful Web Services (Richardson, Ruby) / 適用: REST設計原則 / 目的: 一貫したAPI設計• Web API Design (Brian Mulloy) / 適用: 実践的なAPI設計パターン / 目的: 使いやすいAPITrigger:Use when designing REST APIs, implementing HTTP clients, configuring cache strategies, setting security headers, or ensuring idempotency.http, rest api, status codes, cache-control, cors, idempotency, headers, http/2, keep-alive
performance-optimization
Use when analyzing and improving performance for database queries, API endpoints, or frontend rendering.
signalwire
Use when building telephony, messaging, or video applications; implementing voice AI agents; working with SWML call flows; debugging webhook callbacks or call state issues; setting up real-time WebSocket communication; encountering authentication 401/403 errors; or troubleshooting SWAIG function errors - provides REST API patterns, SDK examples, and production-tested workflows for modern SignalWire communication systems
resource-oriented-api
MCPのリソース指向API設計パターンを提供。URIスキーム設計、リソースモデル定義、プロバイダー実装、キャッシュ戦略、リソース変換パターンを網羅する。Anchors:• RESTful Web APIs (Leonard Richardson) / 適用: リソース設計・URI設計 / 目的: REST原則の適用• MCP Resource Protocol / 適用: リソースプロバイダー実装 / 目的: MCP仕様準拠Trigger:Use when designing MCP resources, implementing resource providers, or defining URI schemes.MCP resource, resource provider, URI scheme, リソース定義, リソースモデル, API設計
performance-optimization
Use when analyzing and improving performance for database queries, API endpoints, or frontend rendering.
json-schema
JSON Schema仕様に基づくスキーマ設計を専門とするスキル。API仕様の定義、OpenAPI連携、バリデーションルールの標準化を通じて、相互運用性の高いデータ構造を設計します。Anchors:• Effective TypeScript (Dan Vanderkam) / 適用: 型安全性とスキーマ設計 / 目的: 堅牢なスキーマ構造の実現• JSON Schema仕様 (Draft 2020-12) / 適用: 標準スキーマ定義 / 目的: 言語非依存なデータバリデーションTrigger:JSONスキーマ定義、APIレスポンス検証、データバリデーション設計、OpenAPI統合、スキーマ継承パターン、複雑なデータ構造の妥当性確認時に使用。
api-generation
Generate TypeScript API client from Swagger/Go comments. Use when updating API endpoints, adding new routes, or regenerating the frontend API client after backend changes.
debug-connection
Debug WebSocket connection issues between CLI and FigJam plugin. Use when diagrams aren't syncing or connection fails.
darkit-gin
基于 gin-gonic/gin 的企业级 Web 框架增强版,提供开箱即用的 JWT 认证、SSE 实时通信、缓存管理、OpenAPI 文档生成等企业级功能。涵盖选项式路由配置、统一响应格式、中间件管理、安全加固、性能优化等完整开发能力。
api-documentation
Master API documentation with REST references, OpenAPI specs, code examples, and developer-friendly API guides.
fastapi-generator
Generates FastAPI endpoints with proper Pydantic models, dependency injection, async handlers, and OpenAPI documentation. Use when building Python REST APIs.