api-patterns▌
sickn33/antigravity-awesome-skills · updated Apr 8, 2026
Structured decision-making framework for selecting and designing APIs across REST, GraphQL, and tRPC patterns.
- ›Provides a content map covering API style selection, resource design, response formats, versioning strategies, authentication, rate limiting, and security testing
- ›Includes decision trees and checklists to guide API type selection based on consumer requirements and project context
- ›Documents anti-patterns (verb-based endpoints, inconsistent responses, exposed errors) alongside
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> |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★38 reviews- ★★★★★Ganesh Mohane· Dec 24, 2024
I recommend api-patterns for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ama Haddad· Dec 24, 2024
api-patterns fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ama Reddy· Dec 20, 2024
Keeps context tight: api-patterns is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★James Diallo· Dec 4, 2024
We added api-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Emma Rahman· Nov 23, 2024
Useful defaults in api-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Emma Li· Nov 15, 2024
Registry listing for api-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ira Ndlovu· Nov 11, 2024
api-patterns is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Liam Bhatia· Nov 3, 2024
I recommend api-patterns for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Omar Huang· Oct 22, 2024
api-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Omar Martinez· Oct 14, 2024
api-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 38