api-design-principles

Plan and execute scalable REST and GraphQL API designs with established principles.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/agigante80/forge-kit --skill api-design-principles-agigante80
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design-principles
Source: https://github.com/agigante80/forge-kit/tree/main/plugins/forge-kit-backend/skills/api-design-principles
Command: npx skills add https://github.com/agigante80/forge-kit --skill api-design-principles-agigante80

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill provides a structured approach to REST and GraphQL API design, helping teams craft clear, scalable, and maintainable interfaces.

Core Features & Use Cases

  • RESTful design principles: Resource-oriented endpoints, correct HTTP methods, consistent naming, and robust versioning.
  • GraphQL design patterns: Schema-first design, typed schemas, resolvers guidelines, and pagination strategies.
  • Best practices & patterns: Error handling, pagination, deprecation, DataLoader usage, testing, and documentation.
  • Use cases include establishing API design standards, reviewing specifications, migrating between paradigms, and publicly documenting APIs for teams.

Quick Start

Draft a standards-compliant REST/GraphQL API design specification for your project.

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 REST and GraphQL API design?

REST and GraphQL API design best practices include resource-oriented endpoints, schema-first design, consistent naming, robust error handling, pagination strategies, and deprecation to build scalable and maintainable interfaces.

How do I design a scalable REST API with proper resource naming and HTTP methods?

Design a scalable REST API by applying resource-oriented endpoints, correct HTTP methods, consistent naming conventions, and robust versioning patterns to ensure maintainable and clear interface growth.

How does GraphQL schema-first design work with resolvers and DataLoader optimization?

GraphQL schema-first design works by defining typed schemas upfront, implementing resolver guidelines, and applying DataLoader-oriented optimization to batch and cache data fetching, preventing N+1 query issues.

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

Handle pagination and errors across REST and GraphQL APIs by enforcing clear, standardized patterns for both paradigms, ensuring consistent error reporting and efficient data retrieval during migration or standardization.

When should I migrate between REST and GraphQL paradigms for my API standards?

Migrate between REST and GraphQL paradigms when establishing new API design standards, reviewing specifications, or publicly documenting interfaces across teams to enforce clear patterns and resolver optimization.

Can I use this approach to establish API documentation standards for my team?

Yes, you can use this approach to establish API documentation standards for your team by applying structured patterns for REST resource design, GraphQL schemas, error handling, and testing to craft maintainable interfaces.