api-design-principles

Define REST and GraphQL API design patterns with schema-first guidance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MeoBaka/MeoPanel-Client --skill api-design-principles-meobaka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design-principles
Source: https://github.com/MeoBaka/MeoPanel-Client/tree/main/.claude/skills/api-design-principles
Command: npx skills add https://github.com/MeoBaka/MeoPanel-Client --skill api-design-principles-meobaka

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Design and governance for REST and GraphQL APIs: establish principled, consistent patterns that prevent drift and accelerate delivery.

Core Features & Use Cases

  • Schema-first guidance for REST and GraphQL design
  • Reusable patterns for pagination, versioning, errors, and docs
  • Practical templates and checklists for API contracts and reviews

Quick Start

Define a REST/GraphQL API plan for a new service by outlining resources, endpoints, versioning strategy, and error payloads.

Frequently Asked Questions about api-design-principles

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

FAQPage Schema
How do I design scalable REST and GraphQL APIs with consistent patterns?

Design scalable REST and GraphQL APIs using a schema-first approach to establish principled, consistent patterns that prevent drift. This method applies reusable templates for resource modeling, pagination, versioning, and structured error payloads to accelerate delivery.

What is the best way to structure GraphQL data-loading and error payloads?

Structure GraphQL data-loading and error payloads by conforming to a schema-first approach with data-loading optimization. Generate structured error payloads and maintainable documentation templates to ensure developer-friendly interfaces and prevent API drift.

How do I apply a schema-first approach to REST API versioning and pagination?

Apply a schema-first approach to REST API versioning and pagination by utilizing reusable patterns and practical checklists for API contracts. Outline resources, endpoints, versioning strategy, and error payloads to model developer-friendly interfaces for real-world scenarios.

Does this API design guidance provide templates for API contract reviews?

Yes, this API design guidance provides practical templates and checklists for API contracts and reviews. It establishes governance for REST and GraphQL APIs by applying reusable patterns for pagination, versioning, errors, and documentation generation.

When do I need structured error payloads and maintainable documentation templates for APIs?

You need structured error payloads and maintainable documentation templates when shaping scalable, developer-friendly REST or GraphQL interfaces. These patterns prevent drift and accelerate delivery during real-world resource modeling and API governance.