api-design-principles

Guide RESTful and GraphQL API design with architecture and versioning principles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ACGSpgp/ACGS --skill api-design-principles-acgspgp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design-principles
Source: https://github.com/ACGSpgp/ACGS/tree/main/.agent/workflows/backend-development/1.2.3/skills/api-design-principles
Command: npx skills add https://github.com/ACGSpgp/ACGS --skill api-design-principles-acgspgp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers master the principles of designing robust and user-friendly REST and GraphQL APIs, ensuring they are intuitive, scalable, and easy to maintain.

Core Features & Use Cases

  • RESTful Design: Learn resource-oriented architecture, HTTP method semantics, and best practices for endpoints.
  • GraphQL Design: Understand schema-first development, query structure, and efficient data fetching.
  • API Versioning: Explore strategies for managing API evolution.
  • Error Handling & Patterns: Implement consistent error responses and common design patterns for both REST and GraphQL.
  • Use Case: When designing a new microservice API, use this Skill to ensure your endpoints follow established RESTful conventions and your GraphQL schema is well-structured and efficient.

Quick Start

Use the api-design-principles skill to review the provided API specification against RESTful design best practices.

Frequently Asked Questions about api-design-principles

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

FAQPage Schema
What are the best practices for RESTful API design and resource-oriented architecture?

RESTful API design best practices involve structuring endpoints around resources, using correct HTTP method semantics, and applying consistent patterns to build intuitive, scalable, and maintainable backend services.

How do I design an efficient GraphQL schema for backend development?

Designing an efficient GraphQL schema requires a schema-first development approach, defining clear query structures, and optimizing data fetching patterns to ensure your backend API remains scalable and maintainable.

What is the best way to handle API versioning and error handling?

The best way to handle API versioning and error handling is to implement consistent error response patterns and strategic versioning rules, ensuring smooth API evolution without breaking existing client integrations.

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

Choose GraphQL over REST for your microservice API when you need efficient, client-driven data fetching with schema-first development, whereas REST is ideal for standard resource-oriented architecture and HTTP semantics.

How do I avoid common API design pitfalls and ensure my endpoints are maintainable?

To avoid common API design pitfalls and ensure maintainable endpoints, review your API specification against established RESTful conventions and GraphQL schema best practices, addressing resource modeling and error consistency.