API Design

Design clear, consistent, and developer-friendly REST APIs.

When NOT to Use

Consuming external APIs — Use api-integration for building clients to call third-party services (Stripe, Twilio, etc.)
Writing tests for APIs — Use testing-strategy for contract tests, integration tests, mocking strategies
Reviewing existing API security — Use security-audit for vulnerability scanning of live endpoints
Designing auth mechanisms that are the whole task — Use security-audit if reviewing, this skill if designing from scratch

Resource-oriented — Design around nouns (resources), not verbs (actions)
Predictable patterns — Consistent URL structure, response format, and behavior
Clear contracts — Explicit schemas, documented errors, versioned endpoints
Developer experience — Meaningful errors, helpful examples, logical defaults