mcpField
A
api-patterns

api-patterns

github.com/davila7Development33.0k486 installsUpdated today
Repository

About api-patterns

api-patterns is a skill for choosing and designing APIs, aimed at developers weighing API styles and implementation decisions. It combines topic-specific reference files with a context-first checklist and an endpoint validation script.

Key features

  1. 01REST, GraphQL, and tRPC selection guidance
  2. 02REST resource and HTTP method guidance
  3. 03Response, errors, and pagination patterns
  4. 04Versioning, authentication, and rate limiting
  5. 05OpenAPI documentation and security testing
  6. 06Endpoint validation script

Use cases

  1. 01Choosing an API style for a project
  2. 02Planning consistent responses and API versioning
  3. 03Selecting authentication and rate-limiting patterns
  4. 04Validating API endpoints

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davila7/claude-code-templates --skill api-patterns

After installing, type/api-patternsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

api-style.md
auth.md
documentation.md
graphql.md
rate-limiting.md
response.md
rest.md
security-testing.md
trpc.md
versioning.md
scripts/
api_validator.py

Details

From the project README

API Patterns

API design principles and decision-making for 2025. Learn to THINK, not copy fixed patterns.

🎯 Selective Reading Rule

Read ONLY files relevant to the request! Check the content map, find what you need.

📑 Content Map

FileDescriptionWhen to Read
api-style.mdREST vs GraphQL vs tRPC decision treeChoosing API type
rest.mdResource naming, HTTP methods, status codesDesigning REST API
response.mdEnvelope pattern, error format, paginationResponse structure
graphql.mdSchema design, when to use, securityConsidering GraphQL
trpc.mdTypeScript monorepo, type safetyTS fullstack projects
versioning.mdURI/Header/Query versioningAPI evolution planning
auth.mdJWT, OAuth, Passkey, API KeysAuth pattern selection
rate-limiting.mdToken bucket, sliding windowAPI protection
documentation.mdOpenAPI/Swagger best practicesDocumentation
security-testing.mdOWASP API Top 10, auth/authz testingSecurity audits

🔗 Related Skills

NeedSkill
API implementation@[skills/backend-development]
Data structure@[skills/database-design]
Security details@[skills/security-hardening]

✅ Decision Checklist

Before designing an API:

  • Asked user about API consumers?
  • Chosen API style for THIS context? (REST/GraphQL/tRPC)
  • Defined consistent response format?
  • Planned versioning strategy?
  • Considered authentication needs?
  • Planned rate limiting?
  • Documentation approach defined?

❌ Anti-Patterns

DON'T:

  • Default to REST for everything
  • Use verbs in REST endpoints (/getUsers)
  • Return inconsistent response formats
  • Expose internal errors to clients
  • Skip rate limiting

DO:

  • Choose API style based on context
  • Ask about client requirements
  • Document thoroughly
  • Use appropriate status codes

Script

ScriptPurposeCommand
scripts/api_validator.pyAPI endpoint validationpython scripts/api_validator.py <project_path>

Comments

Markdown supported