api-design

Originally fromashchupliak/dream-team
Installation
Summary

REST API design patterns covering resource naming, HTTP semantics, pagination, filtering, error handling, and versioning.

  • Resource URLs use plural nouns in kebab-case with semantic HTTP methods; status codes (201, 204, 400, 404, 422, 429) convey intent rather than embedding status in response bodies
  • Supports offset-based pagination for small datasets and cursor-based pagination for scalable, feed-like interfaces; includes filtering via query parameters, sorting, and sparse fieldsets
  • Error responses include structured codes, messages, and field-level details; success responses wrap data in consistent envelopes with optional metadata and pagination links
  • Covers token and API key authentication, resource-level and role-based authorization patterns, and rate limiting with tier-based quotas and Retry-After headers
  • Recommends URL path versioning (/api/v1/) with deprecation timelines; distinguishes breaking changes (new version required) from non-breaking additions (no version bump needed)
SKILL.md

API Design Patterns

Conventions and best practices for designing consistent, developer-friendly REST APIs.

When to Activate

  • Designing new API endpoints
  • Reviewing existing API contracts
  • Adding pagination, filtering, or sorting
  • Implementing error handling for APIs
  • Planning API versioning strategy
  • Building public or partner-facing APIs

Resource Design

URL Structure

# Resources are nouns, plural, lowercase, kebab-case
Related skills
Installs
4.9K
GitHub Stars
179.7K
First Seen
Feb 13, 2026