api-design-patterns

Installation
SKILL.md

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

API Design Patterns

Language-agnostic patterns for designing robust, scalable REST and GraphQL APIs. Focus on solving real problems with simple, maintainable solutions.

Auto-activate when: Working with API routes, endpoints, REST design, GraphQL schemas, OpenAPI/Swagger specs, authentication tokens, API documentation, or discussing endpoint design, versioning strategies, or API architecture.

Philosophy

  • Simple over clever - Choose straightforward patterns that solve the problem
  • Consistency - Apply patterns consistently across endpoints
  • Least Astonishment - APIs should do what their names suggest, nothing more (see ~/.claude/skills/least-astonishment/)
  • Pragmatism - Pick approaches based on actual use cases, not theoretical purity
  • No over-engineering - Don't add features or complexity "just in case"

REST API Design

Related skills

More from ilude/claude-code-config

Installs
7
GitHub Stars
7
First Seen
Jan 23, 2026