Ask Claude to Review Your API Design for Consistency

APIs accumulate inconsistencies over time — plural vs singular resource names, mixed casing, inconsistent response shapes, verbs where nouns should be. Claude can audit your routes and flag problems before they're locked in.

Here are my API routes. Review them for REST conventions, naming consistency,
and any design issues. Flag anything that looks inconsistent or would surprise
a developer using this API for the first time.

GET  /user/list
POST /users/create
GET  /user/:id/get
PUT  /users/update/:id
GET  /posts
POST /post/new
DELETE /posts/remove/:id

Claude will spot the problems immediately — mixed singular/plural, redundant verbs in paths, inconsistent parameter position — and suggest a clean, consistent version.

You can give it more context to get more specific feedback:

We follow JSON:API spec for our responses. Here are three endpoint responses
from different parts of the codebase. Are they consistent with the spec and
with each other?

[paste response samples]

Claude is also useful when you're designing a new API from scratch:

I'm building an API for a multi-tenant SaaS app. Users belong to organisations.
Both users and organisations have resources like projects and documents. What
URL structure would you recommend, and why?

It's much cheaper to fix API design on paper than to version your way around a mistake six months after launch.