backend-dev-guidelines

Standardize Node.js/TypeScript microservice architecture with layered routes, controllers, services, and repositories.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/giosuetedeschi-spec/bobu-website --skill backend-dev-guidelines-giosuetedeschi-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/giosuetedeschi-spec/bobu-website/tree/main/.claude/skills/backend-dev-guidelines
Command: npx skills add https://github.com/giosuetedeschi-spec/bobu-website --skill backend-dev-guidelines-giosuetedeschi-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates architectural drift and inconsistent coding practices across Node.js microservices by providing a centralized, authoritative source for backend development standards.

Core Features & Use Cases

  • Layered Architecture Enforcement: Provides clear guidance on separating routes, controllers, services, and repositories to ensure testability and maintainability.
  • Standardized Error & Config Management: Implements unifiedConfig and Sentry integration patterns to prevent environment variable leakage and ensure robust error tracking.
  • Use Case: When onboarding a new developer or starting a new microservice, use this Skill to ensure the project structure, validation logic, and database access patterns align with the team's mature "Blog API" and "Auth Service" templates.

Quick Start

Use the backend-dev-guidelines skill to generate a new microservice directory structure and configure the base controller and Sentry instrumentation.

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 microservice to separate routes, controllers, services, and repositories?

Layered architecture in Node.js separates routes, controllers, services, and repositories to enforce dependency injection, ensure testability, and maintain strict boundaries between request handling and business logic.

What is the best way to standardize Zod validation and Sentry error tracking across TypeScript microservices?

Standardizing Zod validation and Sentry error tracking across TypeScript microservices involves enforcing consistent implementation patterns through a centralized guideline, preventing environment variable leakage and ensuring robust error monitoring.

How do I prevent architectural drift when onboarding new developers to existing Prisma and Express backend services?

Preventing architectural drift when onboarding developers to Prisma and Express services requires a centralized source for backend standards that aligns new projects with established templates for database access and middleware orchestration.

Does this backend architecture approach work with Prisma for database access and dependency injection?

Yes, this backend architecture approach works with Prisma by ensuring all database access patterns and dependency injection practices adhere to established best practices within Node.js and TypeScript environments.

When do I need a layered separation of concerns for my Node.js backend API?

You need a layered separation of concerns for your Node.js backend API when starting a new microservice or onboarding developers, ensuring consistent validation logic, error tracking, and unifiedConfig management.