Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
ahmed2020se avatar

Api Patterns

  • 1 installs
  • Updated April 11, 2026
  • ahmed2020se/dotfiles

This is a copy of api-patterns by xenitv1 - installs and ranking accrue to the original listing.

api-patterns is a Claude Code skill that guides API design decisions like REST vs GraphQL vs tRPC selection, response formats, versioning, and pagination.

About

api-patterns is a Claude Code skill that guides API design decisions rather than copying fixed templates. It provides a decision tree for REST vs GraphQL vs tRPC and reference files on resource naming, response envelopes, versioning, pagination, authentication, and rate limiting. A pre-design checklist and anti-pattern list steer the agent toward context-appropriate choices, and a bundled validator script checks endpoints.

  • Decision framework for choosing REST vs GraphQL vs tRPC per context
  • Covers response envelopes, versioning, pagination, auth, and rate limiting
  • 7-item pre-design checklist plus anti-pattern guardrails

Api Patterns by the numbers

  • 1 all-time installs (skills.sh)
  • Data as of Jul 7, 2026 (Skillselion catalog sync)
At a glance

api-patterns capabilities & compatibility

Capabilities
api design · rest design · graphql design · api versioning
Use cases
api development
Pricing
Free
From the docs

What api-patterns says it does

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
SKILL.md
Learn to THINK, not copy fixed patterns.
SKILL.md
npx skills add https://github.com/ahmed2020se/dotfiles --skill api-patterns

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
Last updatedApril 11, 2026
Repositoryahmed2020se/dotfiles

What it does

Choose an API style and design consistent response, versioning, auth, and rate-limiting patterns before implementing a backend API.

Who is it for?

Deciding an API style and consistent response, versioning, and auth patterns for a new or evolving backend.

Skip if: Implementing the API code itself or designing the data model; those defer to backend-development and database-design skills.

When should I use this skill?

Choosing an API type, designing REST resources, or planning response format, versioning, or rate limiting.

What you get

A context-appropriate API style with consistent response envelopes, a versioning strategy, and planned rate limiting.

  • An API style decision
  • A consistent response and error format
  • A versioning and rate-limiting plan

By the numbers

  • 10-file content map
  • 7-item pre-design checklist

Files

SKILL.mdMarkdownGitHub ↗

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>

Related skills

FAQ

What does api-patterns help me decide?

Whether to use REST, GraphQL, or tRPC for your context, plus response format, versioning, auth, and rate-limiting choices.

Does it write the API for me?

No. It teaches API design decision-making and defers implementation to a backend-development skill.

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.