Agent skill · software engineering · aiskillstore
backend-dev-guidelines
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
Why this skill is useful
Provides specific architectural patterns and best practices for Node.js/Express/TypeScript microservices that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Backend Development Guidelines Purpose Establish consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js/Express/TypeScript patterns. When to Use This Skill 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 --- Quick Start New Backend Feature Checklist [ ] 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 New Microservice Checklist [ ] Directory structure (see architecture-overview.md) [ ] instrument.ts for Sentry [ ] unifiedConfig setup [ ] BaseController class [ ] Middleware stack [ ] Error boundary [ ] Testing framework --- Architecture Overview Layered Architecture Key Principle: Each layer has ONE responsibility. See architecture-overview.md for complete details. --- Directory Structure Naming Conventions: Controllers: PascalCase - UserController.ts Services: camelCase - userService.ts Routes: camelCase + Routes - userRoutes.ts Repositories: PascalCase + Repository - UserRepository.ts --- Core Principles (7 Key Rules) 1. Routes Only Route, Controllers Control 2. All Controllers Extend BaseController 3. All Errors to Sentry 4. Use unifiedConfig, NEVER process.env 5. Validate All Input with Zod 6. Use Repository Pattern for Data Access 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/backend-dev-guidelines--c98f11