api-design-principles

Standardize REST and GraphQL API design with schema-first patterns.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill api-design-principles-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design-principles
Source: https://github.com/rkz91/coco/tree/main/skills/api-design-principles
Command: npx skills add https://github.com/rkz91/coco --skill api-design-principles-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This guide helps teams design intuitive, scalable, and maintainable REST and GraphQL APIs by providing a consolidated set of principles, patterns, and best practices to prevent common design pitfalls.

Core Features & Use Cases

  • REST Design Principles: resource-oriented endpoints, proper HTTP semantics, versioning strategies.
  • GraphQL Design Principles: schema-first design, strongly typed schemas, queries, mutations, and subscriptions.
  • API Patterns & Best Practices: pagination, error handling, deprecation, and documentation strategies; versioning approaches.
  • Real-World Use Cases: designing new APIs, reviewing specifications, migrating between paradigms, and establishing team standards.

Quick Start

Review the REST and GraphQL design principles and implement the recommended patterns in your next API specification.

Frequently Asked Questions about api-design-principles

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

FAQPage Schema
What are the core principles for designing scalable REST and GraphQL APIs?

Core REST and GraphQL API design principles involve a schema-first approach, resource-oriented endpoints, proper HTTP semantics, and strongly typed schemas to ensure consistency, scalability, and maintainability.

How do I handle API versioning and pagination in REST and GraphQL?

Standardize API versioning and pagination by applying consistent patterns during API design, using established versioning strategies for REST endpoints and structured pagination techniques for GraphQL queries.

What is the best way to standardize error handling across REST and GraphQL APIs?

Standardize API error handling by enforcing consistent patterns and best practices across REST and GraphQL, ensuring predictable developer experiences and maintainable specifications during API design reviews.

When should I choose GraphQL over REST for my API design?

Choosing GraphQL over REST depends on your API design needs, where GraphQL's schema-first design, strongly typed schemas, and query flexibility contrast with REST's resource-oriented endpoints and HTTP semantics.

Can I use these API design principles to review existing specifications?

Yes, you can apply these API design principles during specification reviews to enforce schema-first approaches, validate consistent patterns, and identify areas for improvement in versioning, pagination, and error handling.

How do I establish team standards for API documentation and deprecation?

Establish team API standards by applying consistent documentation strategies and deprecation patterns across REST and GraphQL, using reference materials to guide collective decision-making and maintain design consistency.