Backend API Design Pattern
Implements a standardized RPC-style layered architecture for backend services using Controller, Manager, and Repository patterns.
This skill enforces a structured approach to backend development by implementing a strictly layered RPC-style architecture. It provides Claude with the logic to create clean API contracts, manage complex business transactions within a dedicated Manager layer, and handle data access through specialized Repositories. It includes specific rules for URL naming conventions—avoiding path parameters in favor of query values—and provides patterns for Kotlin-based error handling using the Either type, as well as thread-safe execution patterns for high-performance backend services.
Características Principales
01Provides functional error handling using the Either pattern
02Enforces a strict 3-tier architecture: Controller, Manager, and Repository
0378 GitHub stars
04Standardizes RPC-style URL patterns and resource naming conventions
05Automates database read/write splitting between primary and replica instances
06Implements consistent pagination and response model structures
Casos de Uso
01Refactoring monolithic controllers into clean, layered architectural patterns
02Designing new API endpoints for Micronaut or Spring-based backend services
03Standardizing error handling and response formatting across microservices