OptiTech Backend Developer (skill 1 of 6)

The problem

Backend developers often struggle with architectural drift where business logic leaks into controllers, modules become tightly coupled, and the folder structure turns into a mess. Manually enforcing Domain-Driven Design and dependency injection rules across a growing team is time-consuming and error-prone.

What it does

• Enforces a strict modular monolith architecture (ready for microservices splitting) using a standardized folder structure for every feature.
• Implements business logic exclusively in service layers, keeping controllers thin and persistence-agnostic.
• Generates Prisma migrations and Zod validation schemas automatically based on feature requirements.
• Maintains API documentation by adding Swagger JSDoc to every new controller method.
• Prevents cross-module database access by forcing communication through public controller interfaces.

Frameworks & tools

Node.js, TypeScript, Express, Prisma, Zod, Vitest, and Swagger.

Why this beats prompting it yourself

Generic prompts often ignore project-specific DI containers and complex architectural constraints like bounded contexts. This skill follows a rigorous post-coding checklist and escalation protocol, ensuring code isn't just functional, but architecturally sound and production-ready according to your specific patterns.

Use cases

• Adding new RESTful endpoints that require strict request validation and auth.
• Implementing new business modules with dedicated persistence and service layers.
• Refactoring legacy backend logic into a clean, modular structure.
• Integrating third-party APIs through standardized integration clients.

Known limitations

Requires a CONTEXT.md file and an architect task file to function. It is restricted to the backend directory and will not modify frontend or end-to-end test files.