What architectural pattern does this skill follow?

This skill implements the route-service split pattern, which separates HTTP handling (routes) from core business logic (services) for better maintainability.

Does it handle route registration?

Yes, the skill includes steps to automatically mount the newly created routes within the main server entry point at server/src/index.js.

How does the skill ensure code consistency?

It utilizes predefined templates (template_service.js and template_route.js) and adheres to existing naming conventions found in the repository.

Where are the new backend files located?

Services are generated in the server/src/services/ directory, while routes are placed in server/src/routes/.

Backend API Service Architect

Name: Backend API Service Architect
Author: CheekyCodexConjurer

byCheekyCodexConjurer

API Development

Automates the creation of standardized backend services and routes following a modular controller-service architectural pattern.

About

The Backend API Service Architect skill streamlines the development of server-side functionality by enforcing a strict separation of concerns between routing and business logic. Specifically designed for the Quant-Lab environment, it guides Claude through generating service modules, creating route modules with input validation, and automatically mounting new endpoints in the server index. This ensures that every new API feature follows consistent naming conventions and leverages existing templates, making the codebase easier to test and maintain.

Key Features

Enforcement of the controller-service architectural split
Streamlined endpoint registration in the application entry point
0 GitHub stars
Integrated input validation via contract schemas
Automated generation of route and service modules
Template-based code creation for consistency

Use Cases

Refactoring existing monolithic routes into a clean service-based structure
Adding new RESTful API endpoints for financial data or trading logic
Implementing modular business services that are easy to unit test

About

Key Features

Enforcement of the controller-service architectural split
Streamlined endpoint registration in the application entry point
0 GitHub stars
Integrated input validation via contract schemas
Automated generation of route and service modules
Template-based code creation for consistency

Use Cases

Refactoring existing monolithic routes into a clean service-based structure
Adding new RESTful API endpoints for financial data or trading logic
Implementing modular business services that are easy to unit test