backend-dev-guidelines

Topics in the source

• Backend Development Guidelines
• Purpose
• When to Use This Skill
• Quick Start
• New Backend Feature Checklist
• New Microservice Checklist
• Architecture Overview
• Layered Architecture

Establish consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js/Express/TypeScript patterns. Automatically activates when working on: Creating or modifying routes, endpoints, APIs Building controllers, services, repositories Implementing middleware (auth, validation, error handling) Database operations with Prisma Error tracking with Sentry Input validation with Zod Configuration management Backend testing and refactoring -- [ ] Route: Clean definition, delegate to controller [ ] Controller: Extend BaseController [ ] Service: Business logic with DI [ ] Repository: Database access (if complex) [ ] Validation: Zod schema [ ] Sentry: Error tracking [ ] Tests: Unit + integration tests [ ] Config: Use unifiedConfig [ ] Directory structure (see architecture-overview.md) [ ] instrument.ts for Sentry [ ] unifiedConfig setup [ ] BaseController class [ ] Middleware stack [ ] Error boundary [ ] Testing framework -- Key Principle: Each layer has ONE responsibility. See architecture-overview.md for complete details. -- Naming Conventions: Controllers: PascalCase - UserController.ts Services: camelCase - userService.ts Ro

This is an excerpt. Refer to the complete source and its current requirements.