skills.rest
TruCol270
TruCol270COMMUNITY
Explore all skills by this author →
GitHub

api-design

Enforce consistent REST API design with standardized naming, methods, and error handling.

1|Updated Apr 7, 2026
Search Tags:#versioning#rest#pagination#naming#design-patterns#api-design
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill api-design-trucol270
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/api-design
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill api-design-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

REST API design can be inconsistent across teams, leading to integration confusion, poor developer experience, and brittle systems.

Core Features & Use Cases

  • Standardized resource naming, HTTP methods, and status codes for predictable contracts.
  • Pagination, filtering, and sorting patterns to enable scalable data access.
  • Versioning and error handling guidelines to support public and partner APIs at scale.

Quick Start

Define a consistent REST API contract across your projects.

Frequently Asked Questions about api-design

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

FAQPage Schema
What are the best practices for REST API pagination and filtering?▼

REST API pagination and filtering best practices involve applying standardized patterns for scalable data access. Implementing consistent pagination, filtering, and sorting conventions enables reliable retrieval of large datasets across endpoints.

How should I handle error responses and versioning in public REST APIs?▼

Handle error responses and versioning in public REST APIs by applying strict versioning guidelines and standardized error response formats. This supports scalable public and partner API integrations without breaking existing contracts.

What HTTP status codes and methods should my REST API use?▼

Your REST API should use standard HTTP methods and status codes mapped to resource actions. Enforcing standard HTTP methods ensures predictable contracts for endpoint creation, updates, and deletions.

Why are my REST API contracts inconsistent and causing integration confusion?▼

Inconsistent REST API contracts cause integration confusion due to a lack of standardized resource naming and error handling. Applying consistent design patterns for versioning and pagination prevents these integration failures.

Related Skills

Explore More Software Engineering Skills→
ConradmakerConradmaker

be-api-design

Design REST API contracts with OpenAPI 3.1 schemas and RFC 7807 errors.

Community
Advanced
AZANIRAZANIR
2

qa-api-contract-curator

Generate OpenAPI 3.x specifications and detect breaking changes from API sources.

Community
Advanced
vertivolatamvertivolatam
1

API Gateway & Rate Limiting

Implement API Gateways with Kong and Nginx rate limiting strategies.

Official
Advanced
Camilo8902Camilo8902

rest-to-graphql-migrator

Migrate REST APIs to GraphQL incrementally using schema stitching and REST data source wrappers.

Community
Advanced