api-design

Guide REST API design covering naming, HTTP methods, status codes, and pagination.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/flatrick/mdt --skill api-design-flatrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/flatrick/mdt/tree/main/skills/api-design
Command: npx skills add https://github.com/flatrick/mdt --skill api-design-flatrick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance and best practices for designing consistent, developer-friendly, and production-ready REST APIs, addressing common pitfalls in resource naming, status codes, pagination, filtering, error handling, versioning, and rate limiting.

Core Features & Use Cases

  • Resource Design: Establishes conventions for URL structures and naming.
  • HTTP Semantics: Details correct usage of HTTP methods and status codes.
  • Response Formatting: Offers patterns for success, collection, and error responses.
  • Advanced Features: Covers pagination strategies (offset vs. cursor), filtering, sorting, authentication, authorization, rate limiting, and versioning.
  • Use Case: A backend developer needs to design a new set of endpoints for a user management system and wants to ensure the API is well-structured, secure, and easy for frontend teams to consume.

Quick Start

Use the api-design skill to generate a standard error response structure for a 400 bad request error.

Frequently Asked Questions about api-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What's the best way to structure REST API resource naming conventions?

REST API resource naming conventions should establish clear URL structures and consistent naming patterns to ensure endpoints are well-structured and developer-friendly. This provides a standardized approach for frontend teams to consume.

How do I implement offset vs cursor-based pagination in REST APIs?

Offset vs cursor-based pagination in REST APIs are covered as advanced patterns. Offset pagination uses basic skip and limit parameters, while cursor-based pagination provides more efficient data fetching for large datasets.

What HTTP status codes should I use for REST API success and error responses?

HTTP status codes for REST APIs must detail correct semantic usage for both success and error responses. Using standard HTTP method semantics ensures proper response formatting for 400 bad requests and other common errors.

How do I add rate limiting and authentication patterns to a backend web service?

Rate limiting and authentication patterns for backend web services are implemented to control traffic flow and secure access. These patterns include authorization mechanisms and versioning approaches to maintain production-ready APIs.

Does this API design guide include code examples for TypeScript, Python, and Go?

Code examples for TypeScript, Python, and Go are included throughout the API design guide. These examples demonstrate resource design, response formatting, and filtering mechanisms alongside an API design checklist for pre-launch validation.