backend-dev-guidelines

Standardize Node.js/Express/TypeScript microservice backend implementations with layered architecture.

111|21|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/Dimon94/cc-devflow --skill backend-dev-guidelines-dimon94
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/Dimon94/cc-devflow/tree/main/.claude/skills/_reference-implementations/backend-express-prisma
Command: npx skills add https://github.com/Dimon94/cc-devflow --skill backend-dev-guidelines-dimon94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes consistent best practices for building Node.js/Express/TypeScript microservices, ensuring a layered architecture, robust error handling, and secure database interactions. It streamlines backend development, making services maintainable, testable, and scalable.

Core Features & Use Cases

  • Layered Architecture: Guides on separating concerns into Routes, Controllers, Services, and Repositories for clarity and testability.
  • Prisma & Zod Integration: Provides best practices for database access with Prisma and input validation with Zod, ensuring data integrity.
  • Sentry Error Tracking: Ensures all errors are captured and monitored for proactive issue resolution and improved system reliability.
  • Use Case: A developer needs to create a new user authentication endpoint. This skill provides a checklist for new features, guides on using BaseController, userService, userRepository, and integrating Zod validation and Sentry error tracking.

Quick Start

To create a new backend feature, define a clean route, extend BaseController, implement business logic in a service, and use Zod for input validation.

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 Node.js/Express backend with layered architecture?▼

Layered architecture separates your backend into Routes, Controllers, Services, and Repositories. This structure improves testability and maintainability by isolating concerns: Routes handle HTTP requests, Controllers orchestrate logic, Services contain business rules, and Repositories manage data access through Prisma.

What's the best way to validate user input in Express APIs?▼

Use Zod for runtime input validation in Node.js/Express APIs. Zod provides schema-based validation that catches invalid data before it reaches your services, ensuring data integrity and preventing bugs from malformed requests.

How do I set up error tracking and monitoring in Node.js microservices?▼

Integrate Sentry into your Node.js/Express services to capture and monitor all errors automatically. Sentry tracks exceptions across your microservices, enabling proactive issue resolution and visibility into system reliability.

Can I use Prisma for database access in a TypeScript microservice?▼

Yes. Prisma works seamlessly with TypeScript microservices and provides type-safe database queries. Pair Prisma with a Repository layer to standardize data access patterns and improve code reusability across services.

What should I include when creating a new backend feature?▼

A new feature requires a clean route, a Controller extending BaseController, business logic in a Service, and Zod validation for inputs. This pattern ensures consistency across your microservices and includes integrated error tracking via Sentry.

Why is dependency injection important in backend microservices?▼

Dependency injection decouples services and repositories, making code testable and flexible. It allows you to swap implementations—such as swapping a real database for a mock during testing—without changing your core business logic.