backend-dev-guidelines

Enforce backend development standards across microservices with layered architecture.

317|108|Updated Oct 18, 2025

Search Tags:#testing #architecture #backend #observability #guidelines #dependency-injection

Ready to run

npx skills add https://github.com/AojdevStudio/Finance-Guru --skill backend-dev-guidelines-aojdevstudio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/AojdevStudio/Finance-Guru/tree/main/.claude/skills/backend-dev-guidelines
Command: npx skills add https://github.com/AojdevStudio/Finance-Guru --skill backend-dev-guidelines-aojdevstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend teams often struggle to maintain consistent architecture, patterns, and quality across multiple microservices, leading to duplicated effort and fragmented best practices.

Core Features & Use Cases

Guides on layered architecture (routes → controllers → services → repositories) with BaseController patterns.
Centralizes configuration, error handling, observability, and testing strategies.
Migration guidance from legacy patterns and examples for Express/Prisma to modern Node.js/Express/TypeScript stacks.

Quick Start

Create a new backend feature by applying this playbook to structure routes, controllers, services, repositories, and tests, then align with unified config, DI, and observability 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 structure a scalable Node.js backend with layered architecture?▼

Structure a scalable Node.js backend by separating routes, controllers, services, and repositories. This playbook codifies that layered architecture pattern using a BaseController to standardize request handling and enforce separation of concerns across microservices.

What is the best way to standardize backend configuration and error handling across microservices?▼

Standardize backend configuration and error handling by centralizing them with a unifiedConfig pattern and Sentry integration. This ensures consistent observability and configuration management across all microservices in your stack.

How do I apply dependency injection in a TypeScript Express backend?▼

Apply dependency injection in a TypeScript Express backend to decouple service creation from route controllers. The guidelines prescribe specific DI patterns that maintain consistent architecture and simplify testing across your services.

Can I use this backend architecture playbook to migrate a legacy Express and Prisma application?▼

Yes, you can migrate a legacy Express and Prisma application using the included migration guidance. It provides structured examples for transitioning legacy patterns to modern Node.js, Express, and TypeScript stacks.

When do I need Zod validation in a backend service architecture?▼

You need Zod validation in a backend service architecture to enforce runtime type safety for incoming requests. The guidelines prescribe Zod usage alongside controllers to ensure data integrity before processing business logic.

What testing strategies should I use for Node.js microservices with layered architecture?▼

Use testing strategies that target the isolated layers of your Node.js microservices. The playbook centralizes testing approaches for routes, controllers, services, and repositories to ensure reliable validation across the layered architecture.