API 設計技能

Name: API 設計技能
Availability: InStock
Author: bryantchi

Design REST and GraphQL APIs with consistent naming, pagination, and versioning standards.

1|Updated Jan 22, 2026

Search Tags:#design #versioning #authentication #api #rest #graphql

Ready to run

npx skills add https://github.com/BryantChi/webdev-skills --skill api-bryantchi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: API 設計技能
Source: https://github.com/BryantChi/webdev-skills/tree/main/api
Command: npx skills add https://github.com/BryantChi/webdev-skills --skill api-bryantchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable, consistent APIs to reduce integration friction and maintenance costs.

Core Features & Use Cases

Endpoint naming conventions for REST and GraphQL schemas
Standardized responses, error handling, and status codes
Versioning, pagination, filtering, and authentication strategies
Use Case: teams align on API standards across microservices and public APIs

Quick Start

Create a consistent REST/GraphQL API design by applying these guidelines.

Frequently Asked Questions about API 設計技能

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

FAQPage Schema

How do I design consistent REST and GraphQL APIs for microservices?▼

To design consistent REST and GraphQL APIs for microservices, apply standardized endpoint naming, pagination, filtering, and authentication conventions. This reduces integration friction and maintenance costs across teams and platforms.

What is the best way to implement API versioning and authentication standards?▼

The best way to implement API versioning and authentication standards is to enforce consistent conventions across all public APIs and backend services. Standardized responses and error handling further improve maintainability.

How does API endpoint naming work for REST and GraphQL schemas?▼

API endpoint naming for REST and GraphQL schemas works by applying consistent conventions across all services. This ensures scalable design, standardized responses, and proper status codes for frontend integration.

Can I use these API design conventions for public APIs across different teams?▼

Yes, you can use these API design conventions for public APIs across different teams. The guidelines enforce endpoint naming, versioning, and authentication standards specifically to align microservices and public APIs.

Why does API design need standardized error handling and status codes?▼

API design needs standardized error handling and status codes to reduce integration friction and maintenance costs. Consistent responses across REST and GraphQL endpoints ensure maintainable backend services.