backend-dev-guidelines

Standardize Node.js/Express/TypeScript microservices with layered architecture and error handling.

Updated Aug 27, 2026

Search Tags:#testing #architecture #Node.js #TypeScript #backend #Express #standardize

Ready to run

npx skills add https://github.com/gitcoder27/trading-backtester-v1 --skill backend-dev-guidelines-gitcoder27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/gitcoder27/trading-backtester-v1/tree/main/.agent/skills/backend-dev-guidelines
Command: npx skills add https://github.com/gitcoder27/trading-backtester-v1 --skill backend-dev-guidelines-gitcoder27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies consistent backend architecture, patterns, and best practices to reduce variability across Node.js/Express/TypeScript microservices.

Core Features & Use Cases

BaseController pattern and a clear layered architecture (routes → controllers → services → repositories)
Guidance on Prisma, Sentry, Zod, unifiedConfig, and testing strategies
Comprehensive workflow for error handling, performance monitoring, and migrations

Quick Start

Start by adopting the BaseController pattern in new controllers and applying the layering rules to all new services. Then integrate Prisma repositories, standardize error handling with centralized utilities, and enable startup validation of configuration. Finally, use the provided references to align your middleware, testing, and monitoring practices.

Frequently Asked Questions about backend-dev-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize Node.js and Express backend architecture across microservices?▼

Standardize Node.js and Express backend architecture by enforcing a layered pattern: routes to controllers to services to repositories. Adopt the BaseController pattern for new controllers and apply layering rules to all new services to ensure maintainability and consistency across microservices.

What is the best way to structure Prisma repositories and error handling in TypeScript?▼

The best way to structure Prisma repositories is to integrate them within the repository layer of your architecture. Centralize error handling using provided utilities, and enable startup validation of configuration to align your middleware, testing, and monitoring practices.

Does this backend development approach work with Zod and Sentry for performance monitoring?▼

Yes, this backend development approach works with Zod and Sentry. It provides comprehensive workflows for error handling, performance monitoring, and migrations, specifically offering guidance on integrating Prisma, Sentry, Zod, and unifiedConfig within your microservices.

How do I apply a layered architecture workflow to new Express routes and controllers?▼

Apply a layered architecture workflow by creating new routes that direct traffic to controllers. Controllers should then delegate business logic to services, which interact with repositories. This reduces variability and enforces consistency across your Node.js and TypeScript backend.

When do I need centralized configuration validation in Node.js microservices?▼

You need centralized configuration validation in Node.js microservices when you want to prevent startup failures from invalid settings. Enabling startup validation of configuration using unifiedConfig ensures that your backend services fail fast if required environment variables or settings are missing.