backend-dev-guidelines

Enforce layered architecture and error-handling standards for Node.js Express microservices.

Updated May 5, 2026

Search Tags:#typescript #backend #microservices #zod #sentry #prisma #express

Ready to run

npx skills add https://github.com/Movchanets/Microservices_Learning --skill backend-dev-guidelines-movchanets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/backend-dev-guidelines
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill backend-dev-guidelines-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents brittle backend implementations by enforcing a consistent, production-grade way to structure services, handle errors, validate input, and manage configuration.

Core Features & Use Cases

It provides strict guidance for routes, controllers, services, repositories, middleware, validation, and observability in Node.js and TypeScript backend systems. It is useful when building or refactoring Express microservices, Prisma-backed data access layers, Zod validation flows, and Sentry-based error monitoring. It helps teams keep business logic out of routes, preserve testability, and maintain clean architectural boundaries across growing codebases.

Quick Start

Use this skill to review a backend feature and rewrite it into a layered, validated, observable implementation that follows the repository’s production standards.

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 Express microservices with TypeScript to keep business logic out of routes?▼

Structure Express microservices by enforcing layered separation with distinct routes, controllers, services, and repositories. This approach moves business logic out of routes, preserves testability, and maintains clean architectural boundaries across growing Node.js codebases.

What is the best way to validate input in Node.js backend services?▼

Validate input in Node.js backend services using Zod validation flows. This enforces consistent, production-grade data validation for routes and controllers, preventing brittle implementations and ensuring safe data processing.

How does Prisma repository-based data access work in a layered backend architecture?▼

Prisma repository-based data access isolates database operations within a dedicated repository layer. This enforces strict separation from services and controllers, preserving testability and maintaining clean architectural boundaries in TypeScript microservices.

Can I use Sentry for error monitoring and observability in Express microservices?▼

Yes, you can use Sentry for error monitoring and observability in Express microservices. Implementing Sentry capture enforces production-grade error-handling standards and centralized configuration across your Node.js backend architecture.

When do I need dependency injection in Node.js TypeScript backend systems?▼

You need dependency injection in Node.js TypeScript backend systems when enforcing production-grade architecture. It preserves testability, maintains clean boundaries, and ensures strict layered separation across controllers, services, and repositories.