Backend API

REST API design should enforce authentication mechanisms, validate all inputs, use HTTPS, implement rate limiting, and follow consistent naming conventions. This Skill guides endpoint creation, request/response formats, and security patterns to ensure your APIs are robust and standardized across your backend services.

API documentation should clearly specify endpoints, request parameters, response schemas, error codes, and authentication requirements. This Skill ensures your documentation adheres to project standards, making it easier for other services and frontend applications to consume your APIs reliably.

Consistent error handling means defining standard HTTP status codes, error response formats, and validation rules across all endpoints. This Skill applies coding standards to your backend API files, ensuring robust error responses that clients can parse and act on predictably.

This Skill covers REST, GraphQL, and gRPC APIs, along with internal backend APIs. It applies standardized design, security, and error-handling patterns across all these protocol types, ensuring consistency regardless of which integration approach your services use.

Backend APIs should implement authentication mechanisms aligned with project standards—such as API keys, OAuth, JWT tokens, or mutual TLS. This Skill guides you to select and configure the appropriate mechanism for your service context and security requirements.

Standardized APIs use consistent endpoint naming, request/response schemas, error formats, and documentation. This reduces integration friction, enables faster client development, and minimizes bugs caused by unclear or inconsistent interfaces across your backend ecosystem.