mcpbeat

API Patterns

dokhacgiakhoa/api-patterns

API design principles and decision-making.

5k tokens
context cost
the whole folder, loaded on every use
12
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill api-patterns

What comes with it

18 121 bytes besides the instruction
api-style.md
auth.md
documentation.md
graphql.md
rate-limiting.md
response.md
rest.md
scripts/api_validator.py
security-testing.md
trpc.md
versioning.md

The instruction itself

7 sections, as written by the author

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

| File | Description | When to Read |

|------|-------------|--------------|

| api-style.md | REST vs GraphQL vs tRPC decision tree | Choosing API type |

| rest.md | Resource naming, HTTP methods, status codes | Designing REST API |

| response.md | Envelope pattern, error format, pagination | Response structure |

| graphql.md | Schema design, when to use, security | Considering GraphQL |

| trpc.md | TypeScript monorepo, type safety | TS fullstack projects |

| versioning.md | URI/Header/Query versioning | API evolution planning |

| auth.md | JWT, OAuth, Passkey, API Keys | Auth pattern selection |

| rate-limiting.md | Token bucket, sliding window | API protection |

| documentation.md | OpenAPI/Swagger best practices | Documentation |

| security-testing.md | OWASP API Top 10, auth/authz testing | Security audits |


| Need | Skill |

|------|-------|

| 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

| Script | Purpose | Command |

|--------|---------|---------|

| scripts/api_validator.py | API endpoint validation | python scripts/api_validator.py <project_path> |

How to use it

Copy the folder

Take dokhacgiakhoa/api-patterns from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.