design-apis

Guide API design across REST, GraphQL, and gRPC with versioning and error handling.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill design-apis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-apis
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/design-apis
Command: npx skills add https://github.com/lushly-dev/afd --skill design-apis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert guidance to design and review APIs, ensuring they are robust, maintainable, and easily consumable by both human developers and AI agents.

Core Features & Use Cases

  • API Design Guidance: Covers REST, GraphQL, and gRPC, including naming conventions, versioning, and error handling.
  • Agent-Friendly Patterns: Focuses on making APIs discoverable and usable by AI agents through OpenAPI and MCP integration.
  • Use Case: You are designing a new microservice API. Use this Skill to ensure your REST API follows best practices for resource modeling, error responses (RFC 9457), and includes an OpenAPI 3.1 spec that AI agents can easily consume.

Quick Start

Use the design-apis skill to get guidance on designing a REST API with versioning and error handling best practices.

Frequently Asked Questions about design-apis

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

FAQPage Schema
How do I design a REST API with proper versioning and error handling?

To design a REST API with versioning and error handling, follow resource modeling best practices and use RFC 9457 for standardized error responses. This ensures your API is robust, maintainable, and easily consumable by human developers.

What is an agent-friendly API and how does OpenAPI 3.1 help?

An agent-friendly API is discoverable and usable by AI agents through OpenAPI 3.1 specification authoring and MCP tool integration. OpenAPI 3.1 provides a machine-readable contract that AI agents can easily parse to understand and interact with your endpoints.

When should I use gRPC vs GraphQL vs REST for my API?

Choosing between gRPC, GraphQL, and REST depends on your use case, as this Skill provides comprehensive design guidance across all three paradigms. REST suits resource modeling, GraphQL handles flexible data fetching, and gRPC optimizes high-performance inter-service communication.

How do I implement pagination and OAuth 2.1 security in my API?

Implement pagination and OAuth 2.1 security by following established API design patterns for rate limiting and access control. This Skill addresses these critical security considerations alongside pagination strategies to ensure robust resource protection.

What are the best practices for API naming conventions and resource modeling?

API naming conventions and resource modeling best practices involve creating logical, consistent endpoint structures that clearly represent your domain entities. This Skill provides comprehensive guidance to ensure your API design follows industry standards.

Can I use this guidance to review an existing microservice API?

Yes, you can use this guidance to review an existing microservice API for robustness and maintainability. The Skill helps evaluate your current API against best practices for resource modeling, error responses, and agent-friendly design.