api-patterns▌
davila7/claude-code-templates · updated Apr 8, 2026
API design principles and decision-making for 2025.
- ›Learn to THINK, not copy fixed patterns.
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 |
🔗 Related Skills
| 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> |
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★50 reviews- ★★★★★Hassan Robinson· Dec 28, 2024
Registry listing for api-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Valentina Diallo· Dec 28, 2024
Keeps context tight: api-patterns is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kaira Bansal· Dec 24, 2024
Useful defaults in api-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kabir Taylor· Dec 24, 2024
api-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Shikha Mishra· Dec 16, 2024
I recommend api-patterns for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★William Rahman· Dec 8, 2024
We added api-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ava Bhatia· Nov 27, 2024
api-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Anaya Kapoor· Nov 19, 2024
api-patterns is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakshi Patil· Nov 15, 2024
Useful defaults in api-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sakura Khan· Nov 15, 2024
Solid pick for teams standardizing on skills: api-patterns is focused, and the summary matches what you get after install.
showing 1-10 of 50