api-design
Skill1 starsChanged 6 months agoMITView on GitHub
Use when designing or reviewing REST APIs — covers URL conventions, status codes, response envelopes, pagination, and auth headers.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- RostislavDugin/postgresustheir own version, first seen Nov 8, 2026
- Markssuave/Markssuave-Agent-skillstheir own version, first seen Nov 8, 2026
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- databasus/databasustheir own version, first seen Nov 8, 2026
- lhbsaa/apex-unifiedtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use db-design, everything-claude-code and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
yuexueyuSkilldb-design
数据库工程师技能 - Schema设计、索引优化、并发安全、数据库审计。当你涉及数据库表/字段/索引/SQL/迁移/MCP数据库操作、建表改表、写查询时必须使用此技能。即使用户只是说"加个字段"或"查下数据",也应触发。
Also in 4 projects that use this
InfopibeSkilleverything-claude-code
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
tpavanipradeepSkillnextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Also in 15 projects that use this
Indium-AI-LabsSkilldata-pipeline-design
Design batch or incremental ETL and ELT pipelines and warehouse models: grain, partitioning, idempotent loads, late-arriving data, data quality tests, PII controls, and cost monitoring, before building them. Use when adding or changing a dbt model, warehouse table, scheduled transformation, or ingestion job. Not for transactional schema design (use the database-design skill) or event-sourced stores (use the event-sourcing-architecture skill).
Also in 3 projects that use this
thejordanleopoldSkillthird-party-integration
Use when integrating with external APIs, payment processors (Stripe), webhooks, or third-party services. Use when implementing API clients with authentication and rate limiting, handling webhooks with signature verification and idempotency, writing contract tests for external services, or isolating third-party dependencies behind adapters. Triggers: \"Stripe\", \"payment integration\", \"webhook\", \"third-party API\", \"external service\", \"API client\", \"integrate with\", \"signature verification\", \"idempotency key\".
Also in 3 projects that use this
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- affaan-m/ECC★ 246ksame name
- databasus/databasus★ 9.3ksame name
- RostislavDugin/postgresus★ 9.3ksame name
- authgear/authgear-server★ 2.1ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- Aaronontheweb/dotnet-skills★ 1.2ksame name
- epam/ai-dial-chat★ 501same name
- loulanyue/awesome-claude-notes★ 272same name
- KbWen/agentic-os★ 229same name
- DevelopersGlobal/ai-agent-skills★ 216same name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- brainstormSkill
- code-reviewSkill
- commitSkill
- evaluate-feedbackSkill
- go-apiSkill
- multi-agentSkill
- planSkill
- tddSkill
- ts-apiSkill
- workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 165 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
All responses use this shape:
- Distinctive: line 78
Use cursor-based pagination for all list endpoints:
- Distinctive: line 81
Default limit: 20; max limit: 100
- Very specific: line 85
Never use offset-based pagination (?page=2) — it breaks under concurrent inserts/deletes.
- Distinctive: line 90
Never accept tokens in query params or cookies for APIs
“Common” is measured: kept by at least 6 in 10 of the 165 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
API Design
REST API design standards shared across TypeScript and Golang web APIs. Apply these conventions in all new endpoints and when reviewing existing ones.
Recommended model: Haiku (reference lookups and convention checks)
URL Conventions
- Resource names: plural nouns, lowercase, kebab-case —
/users,/marketing-plans - No verbs in URLs — actions are expressed via HTTP method, not path
- Nested resources:
/users/{id}/posts— nest only one level deep - Path parameters:
{id}not:idin docs; use framework convention in code - Versioning:
/v1/prefix on all routes —/v1/users/{id}
HTTP Methods
| Method | Meaning | Success code |
| GET | Read resource(s) | 200 |
| POST | Create resource | 201 |
| PUT | Replace resource | 200 |
| PATCH | Partial update | 200 |
| DELETE | Remove resource | 204 (no body) |
Response Envelope
All responses use this shape:
{
"data": { ... } | null,
"error": { "code": "string", "message": "string", "details": {} } | null,
"meta": { "nextCursor": "string", "total": 100 }
}dataisnullwhen there is an errorerrorisnullon successmetais included only for paginated responses
Error Shape
{
"code": "VALIDATION_ERROR",
"message": "Human-readable description",
"details": { "field": "reason" }
}Standard error codes: VALIDATION_ERROR, UNAUTHORIZED, FORBIDDEN, NOT_FOUND, CONFLICT, RATE_LIMITED, INTERNAL_ERROR
HTTP Status Codes
| Code | When |
| 200 | Successful GET, PUT, PATCH |
| 201 | Resource created (POST) |
| 204 | Successful DELETE (no body) |
| 400 | Bad request / malformed input |
| 401 | Missing or invalid auth token |
| 403 | Authenticated but not authorized |
| 404 | Resource not found |
| 409 | Conflict (duplicate, state mismatch) |
| 422 | Validation failed (valid JSON, invalid business rules) |
| 429 | Rate limit exceeded |
| 500 | Unexpected server error |
Pagination
Use cursor-based pagination for all list endpoints:
- Request:
GET /v1/posts?after=<cursor>&limit=20 - Default limit: 20; max limit: 100
- Response
meta:{ "nextCursor": "<opaque>", "total": 500 } nextCursorisnullwhen no more pages
Never use offset-based pagination (?page=2) — it breaks under concurrent inserts/deletes.
Authentication
- Token in
Authorization: Bearer <jwt>header only - Never accept tokens in query params or cookies for APIs
- Validate in middleware before hitting route handlers
Rate Limiting
- Respond with
429when limit exceeded - Include headers:
X-RateLimit-Limit,X-RateLimit-Remaining,Retry-After(seconds)
Naming
- Request/response field names:
camelCasein JSON (TypeScript) orsnake_case(Go withjson:"field_name"tags) - Timestamps: ISO 8601 UTC —
"2024-01-15T10:30:00Z" - IDs: strings (not integers) — use CUID, UUID, or nanoid
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

