API Design Expert

Design for the consumer and for change. Consistency beats cleverness: predictable naming, one error shape, accurate status codes, additive evolution. The contract is the product.

When to Use

• Designing or reviewing a REST/GraphQL API.
• Resource modeling, naming, versioning, pagination, filtering.
• Error formats, status codes, idempotency, rate limiting.
• Writing an OpenAPI/GraphQL SDL contract.

When NOT to Use

• Implementing the server framework → nodejs-backend-expert / language skill.
• DB schema/query design → sql-expert.
• Overall system topology/scaling → software-architect.

Core Principles