api-design

Design and validate REST and GraphQL APIs using contract-first principles.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/xiaoshuangLi/aibo --skill api-design-xiaoshuangli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/xiaoshuangLi/aibo/tree/main/skills/api-design
Command: npx skills add https://github.com/xiaoshuangLi/aibo --skill api-design-xiaoshuangli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and review APIs that are consistent, scalable, and easy to evolve across REST and GraphQL, reducing contractual drift and integration friction.

Core Features & Use Cases

  • REST and GraphQL design principles, versioning strategies, and contract-first development guidance.
  • HTTP methods, resource naming, status codes, pagination, and filtering to ensure predictable APIs.
  • OpenAPI/Swagger documentation, API design reviews, and migration planning for evolving interfaces.
  • Authentication and authorization patterns, deprecation practices, and governance for API contracts.

Quick Start

Draft an OpenAPI specification for your API and follow contract-first design to align REST and GraphQL choices.

Frequently Asked Questions about api-design

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

FAQPage Schema
What is contract-first API design and how does it reduce integration friction?

Contract-first API design involves drafting an OpenAPI specification before writing code, ensuring consistent REST and GraphQL contracts. This approach reduces contractual drift and minimizes integration friction by aligning interface choices early across enterprise scenarios.

How do I design REST APIs with proper HTTP methods, status codes, and pagination?

To design REST APIs, apply standard HTTP methods, predictable resource naming, correct status codes, and efficient pagination. Following these design principles ensures your API remains consistent, scalable, and easy to evolve while maintaining predictable filtering behaviors.

What's the best way to version REST and GraphQL APIs during migration?

The best way to version APIs during migration involves using structured versioning strategies and deprecation practices. Planning your API migration with clear governance ensures evolving REST and GraphQL interfaces remain backward-compatible without breaking existing integrations.

How do I document an OpenAPI specification for secure authentication patterns?

To document an OpenAPI specification, define secure authentication and authorization patterns directly within your contract. Generating OpenAPI/Swagger documentation ensures your API design reviews capture necessary security governance for evolving interfaces.

Can I use contract-first design for both REST and GraphQL enterprise scenarios?

Yes, contract-first design applies to both REST and GraphQL across common enterprise scenarios. It guides naming, versioning, and status code choices, ensuring predictable APIs and secure authentication patterns regardless of the protocol used.