backend-guidelines

Enforce layered backend architecture patterns across Node.js microservices.

Updated Oct 15, 2025
One-click install
npx skills add https://github.com/Italo520/erp_archflow_arquiteture --skill backend-guidelines-italo520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-guidelines
Source: https://github.com/Italo520/erp_archflow_arquiteture/tree/main/.agent/skills/backend-guidelines
Command: npx skills add https://github.com/Italo520/erp_archflow_arquiteture --skill backend-guidelines-italo520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js/Express/TypeScript patterns.

Core Features & Use Cases

  • Clear architecture guidelines for routes, controllers, services, repositories, and middleware.
  • Standards for error handling, input validation with Zod, Sentry integration, and dependency injection.
  • Real-world use: ensures scalable backend teams adopt uniform patterns across microservices.

Quick Start

Implement a new backend feature following the New Backend Feature Checklist and New Microservice Checklist, ensuring routes delegate to controllers, controllers extend BaseController, services use DI, and Prisma, Sentry, and unifiedConfig are wired properly.

Frequently Asked Questions about backend-guidelines

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

FAQPage Schema
How do I standardize backend patterns across Node.js microservices?

Apply a layered Node.js architecture where routes delegate to controllers, controllers extend BaseController, and services use dependency injection with Zod validation to enforce consistent backend patterns across microservices.

What is the best way to structure Express routes and controllers in TypeScript?

Structure Express routes and controllers by having routes delegate directly to controllers that extend BaseController, ensuring services handle business logic and repositories manage Prisma-based data access.

How does dependency injection work with Prisma and Zod in a Node.js service?

Dependency injection works by injecting Prisma-based repositories and Zod-validated inputs into service layers, keeping controllers lightweight through BaseController inheritance and unifiedConfig wiring.

Can I use this layered architecture approach for refactoring existing microservices?

Yes, you can refactor existing microservices by applying the New Backend Feature Checklist to migrate routes, controllers, and services into the layered architecture using BaseController, dependency injection, and Sentry monitoring.

When do I need unifiedConfig and Sentry integration in my Express backend?

You need unifiedConfig and Sentry integration when wiring new microservices to ensure standardized configuration management and runtime error monitoring across all backend Node.js services.