dev-api-design

Production-grade API design patterns for REST, GraphQL, and gRPC. Covers API architecture, OpenAPI/Swagger specs, versioning strategies, authentication flows, rate limiting, pagination, error handling, and documentation best practices for modern API development.

$ インストール

git clone https://github.com/vasilyu1983/AI-Agents-public /tmp/AI-Agents-public && cp -r /tmp/AI-Agents-public/frameworks/claude-code-kit/framework/skills/dev-api-design ~/.claude/skills/AI-Agents-public

// tip: Run this command in your terminal to install the skill


name: dev-api-design description: Production-grade API design patterns for REST, GraphQL, and gRPC. Covers API architecture, OpenAPI/Swagger specs, versioning strategies, authentication flows, rate limiting, pagination, error handling, and documentation best practices for modern API development.

API Development & Design — Quick Reference

This skill provides execution-ready patterns for designing, implementing, and documenting production-grade APIs. Claude should apply these patterns when users need REST API design, GraphQL schemas, OpenAPI specifications, API versioning, authentication flows, or API documentation.

Modern Best Practices (2025): OpenAPI 3.1, GraphQL Federation, gRPC for high-performance services, API-first development, contract testing, API gateways, rate limiting with Redis, JWT/OAuth2 patterns, and docs-as-code workflows.


When to Use This Skill

Claude should invoke this skill when a user requests:

  • REST API design and endpoint structure
  • GraphQL schema design and resolver patterns
  • gRPC service definitions and protocol buffers
  • OpenAPI/Swagger specification creation
  • API versioning strategies (URL, header, content negotiation)
  • Authentication and authorization flows (JWT, OAuth2, API keys)
  • Rate limiting, throttling, and quota management
  • API pagination, filtering, and sorting patterns
  • Error response standardization
  • API documentation and developer portals
  • API security best practices (OWASP API Security Top 10)
  • API testing strategies (contract testing, mock servers)
  • API gateway configuration and management

Quick Reference

TaskPattern/ToolKey ElementsWhen to Use
Design REST APIRESTful DesignNouns (not verbs), HTTP methods, proper status codesResource-based APIs, CRUD operations
Version APIURL Versioning/api/v1/resource, /api/v2/resourceBreaking changes, client migration
Paginate resultsCursor-Basedcursor=eyJpZCI6MTIzfQ&limit=20Real-time data, large collections
Handle errorsRFC 7807 Problem Detailstype, title, status, detail, errors[]Consistent error responses
AuthenticateJWT BearerAuthorization: Bearer <token>Stateless auth, microservices
Rate limitToken BucketX-RateLimit-* headers, 429 responsesPrevent abuse, fair usage
Document APIOpenAPI 3.1Swagger UI, Redoc, code samplesInteractive docs, client SDKs
Flexible queriesGraphQLSchema-first, resolvers, DataLoaderClient-driven data fetching
High-performancegRPC + ProtobufBinary protocol, streamingInternal microservices

Decision Tree: Choosing API Style

User needs: [API Type]
    ├─ Public API for third parties?
    │   └─ REST with OpenAPI docs (broad compatibility)
    │
    ├─ Internal microservices?
    │   ├─ High throughput required? → **gRPC** (binary, fast)
    │   └─ Simple CRUD? → **REST** (easy to debug)
    │
    ├─ Client needs flexible queries?
    │   ├─ Real-time updates? → **GraphQL Subscriptions** or **WebSockets**
    │   └─ Complex data fetching? → **GraphQL** (avoid over-fetching)
    │
    ├─ Mobile/web clients?
    │   ├─ Many entity types? → **GraphQL** (single endpoint)
    │   └─ Simple resources? → **REST** (cacheable)
    │
    └─ Streaming or bidirectional?
        └─ **gRPC** (HTTP/2 streaming) or **WebSockets**

Navigation: Core API Patterns

RESTful API Design

Resource: resources/restful-design-patterns.md

  • Resource-based URLs with proper HTTP methods (GET, POST, PUT, PATCH, DELETE)
  • HTTP status code semantics (200, 201, 404, 422, 500)
  • Idempotency guarantees (GET, PUT, DELETE)
  • Stateless design principles
  • URL structure best practices (collection vs resource endpoints)
  • Nested resources and action endpoints

Pagination, Filtering & Sorting

Resource: resources/pagination-filtering.md

  • Offset-based pagination (simple, static datasets)
  • Cursor-based pagination (real-time feeds, recommended)
  • Page-based pagination (UI with page numbers)
  • Query parameter filtering with operators (_gt, _contains, _in)
  • Multi-field sorting with direction (-created_at)
  • Performance optimization with indexes

Error Handling

Resource: resources/error-handling-patterns.md

  • RFC 7807 Problem Details standard
  • HTTP status code reference (4xx client errors, 5xx server errors)
  • Field-level validation errors
  • Trace IDs for debugging
  • Consistent error format across endpoints
  • Security-safe error messages (no stack traces in production)

Authentication & Authorization

Resource: resources/authentication-patterns.md

  • JWT (JSON Web Tokens) with refresh token rotation
  • OAuth2 Authorization Code Flow for third-party auth
  • API Key authentication for server-to-server
  • RBAC (Role-Based Access Control)
  • ABAC (Attribute-Based Access Control)
  • Resource-based authorization (user-owned resources)

Rate Limiting & Throttling

Resource: resources/rate-limiting-patterns.md

  • Token Bucket algorithm (recommended, allows bursts)
  • Fixed Window vs Sliding Window
  • Rate limit headers (X-RateLimit-*)
  • Tiered rate limits (free, paid, enterprise)
  • Redis-based distributed rate limiting
  • Per-user, per-endpoint, and per-API-key strategies

Navigation: Extended Resources

API Design & Best Practices

GraphQL & gRPC

OpenAPI & Documentation

LLM/Agent API Patterns


Navigation: Templates

Production-ready, copy-paste API implementations with authentication, database, validation, and docs.

Framework-Specific Templates

Cross-Platform Patterns

  • api-patterns-universal.md - Universal patterns for all frameworks
    • Authentication strategies, pagination, caching, versioning, validation

External Resources

See data/sources.json for:

  • Official REST, GraphQL, gRPC documentation
  • OpenAPI/Swagger tools and validators
  • API design style guides (Google, Microsoft, Stripe)
  • Security standards (OWASP API Security Top 10)
  • Testing tools (Postman, Insomnia, Paw)

Quick Decision Matrix

ScenarioRecommendation
Public API for third partiesREST with OpenAPI docs
Internal microservicesgRPC for performance, REST for simplicity
Client needs flexible queriesGraphQL
Real-time updatesGraphQL Subscriptions or WebSockets
Simple CRUD operationsREST
Complex data fetchingGraphQL
High throughput requiredgRPC
Mobile/web clientsREST or GraphQL

Anti-Patterns to Avoid

  • Verbs in URLs: /getUserById/users/:id
  • Ignoring HTTP methods: Using GET for mutations
  • No versioning: Breaking changes without version bump
  • Inconsistent error format: Different error structures per endpoint
  • Missing pagination: Returning unbounded lists
  • No rate limiting: Allowing unlimited requests
  • Poor documentation: Missing examples, outdated specs
  • Security by obscurity: Not using HTTPS, weak auth

Related Skills

This skill works best when combined with other specialized skills:

Backend Development

  • software-backend - Production backend patterns (Node.js, Python, Java frameworks)
    • Use when implementing API server infrastructure
    • Covers database integration, middleware, error handling

Security & Authentication

  • software-security-appsec - Application security patterns
    • Critical for securing API endpoints
    • Covers OWASP vulnerabilities, authentication flows, input validation

Database & Data Layer

  • data-sql-optimization - SQL optimization and database patterns
    • Essential for API performance (query optimization, indexing)
    • Use when APIs interact with relational databases

Testing & Quality

  • testing-automation - Test strategy and automation
    • Contract testing for API specifications
    • Integration testing for API endpoints

DevOps & Deployment

  • ops-devops-platform - Platform engineering and deployment
    • API gateway configuration
    • CI/CD pipelines for API deployments

Documentation

  • docs-technical-writing - Technical documentation standards
    • API reference documentation structure
    • Complements OpenAPI auto-generated docs

Architecture

Performance & Observability


Usage Notes

For Claude:

  • Apply RESTful principles by default unless user requests GraphQL/gRPC
  • Always include pagination for list endpoints
  • Use RFC 7807 format for error responses
  • Include authentication in all templates (JWT or API keys)
  • Reference framework-specific templates for complete implementations
  • Link to relevant resources for deep-dive guidance

Success Criteria: APIs are discoverable, consistent, well-documented, secure, and follow HTTP/GraphQL semantics correctly.

Repository

vasilyu1983
vasilyu1983
Author
vasilyu1983/AI-Agents-public/frameworks/claude-code-kit/framework/skills/dev-api-design
21
Stars
6
Forks
Updated2d ago
Added5d ago