agentleFS
mmNalakammNalaka/nm-skills/skills/api-design/SKILL.md

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

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.
  • yuexueyuSkill

    db-design

    数据库工程师技能 - Schema设计、索引优化、并发安全、数据库审计。当你涉及数据库表/字段/索引/SQL/迁移/MCP数据库操作、建表改表、写查询时必须使用此技能。即使用户只是说"加个字段"或"查下数据",也应触发。

    Also in 4 projects that use this

  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • tpavanipradeepSkill

    nextjs-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-LabsSkill

    data-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

  • thejordanleopoldSkill

    third-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

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
  1. Distinctive:

    All responses use this shape:

    line 34
  2. Distinctive:

    Use cursor-based pagination for all list endpoints:

    line 78
  3. Distinctive:

    Default limit: 20; max limit: 100

    line 81
  4. Very specific:

    Never use offset-based pagination (?page=2) — it breaks under concurrent inserts/deletes.

    line 85
  5. Distinctive:

    Never accept tokens in query params or cookies for APIs

    line 90

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 :id in docs; use framework convention in code
  • Versioning: /v1/ prefix on all routes — /v1/users/{id}

HTTP Methods

MethodMeaningSuccess code
GETRead resource(s)200
POSTCreate resource201
PUTReplace resource200
PATCHPartial update200
DELETERemove resource204 (no body)

Response Envelope

All responses use this shape:

{
  "data": { ... } | null,
  "error": { "code": "string", "message": "string", "details": {} } | null,
  "meta": { "nextCursor": "string", "total": 100 }
}
  • data is null when there is an error
  • error is null on success
  • meta is 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

CodeWhen
200Successful GET, PUT, PATCH
201Resource created (POST)
204Successful DELETE (no body)
400Bad request / malformed input
401Missing or invalid auth token
403Authenticated but not authorized
404Resource not found
409Conflict (duplicate, state mismatch)
422Validation failed (valid JSON, invalid business rules)
429Rate limit exceeded
500Unexpected 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 }
  • nextCursor is null when 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 429 when limit exceeded
  • Include headers: X-RateLimit-Limit, X-RateLimit-Remaining, Retry-After (seconds)

Naming

  • Request/response field names: camelCase in JSON (TypeScript) or snake_case (Go with json:"field_name" tags)
  • Timestamps: ISO 8601 UTC — "2024-01-15T10:30:00Z"
  • IDs: strings (not integers) — use CUID, UUID, or nanoid

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.