backend-dev-guidelines

Standardize Node.js/Express/TypeScript microservices with layered architecture, Zod validation, and Sentry error tracking.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thomas0369/claude_ai --skill backend-dev-guidelines-thomas0369
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/thomas0369/claude_ai/tree/main/skills/backend-dev-guidelines
Command: npx skills add https://github.com/thomas0369/claude_ai --skill backend-dev-guidelines-thomas0369

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires express, zod, @prisma/client, @sentry/node, ini, async_hooks, uuidv4, jsonwebtoken, cookie-parser, and includes references (resource) components.

What problem does it solve?

Developing scalable, maintainable, and error-resilient backend microservices can be challenging due to inconsistent patterns, poor error handling, and lack of clear architecture. This Skill provides a unified approach to building robust Node.js/Express/TypeScript backends.

Core Features & Use Cases

  • Layered Architecture: Enforces a clear separation of concerns (Routes → Controllers → Services → Repositories) for enhanced testability, maintainability, and reusability.
  • Robust Error Handling & Monitoring: Integrates Sentry for comprehensive error tracking and performance monitoring, ensuring no error goes unnoticed and providing deep insights into application health.
  • Type-Safe Development: Mandates Zod for input validation and unifiedConfig for type-safe configuration, eliminating common runtime errors and improving developer confidence.
  • Use Case: When developing a new API endpoint, use this skill to ensure the route, controller, service, and repository layers are correctly implemented, input is validated with Zod, and all errors are automatically tracked by Sentry, saving debugging time and ensuring compliance with best practices.

Quick Start

Help me create a new Node.js/Express API endpoint for user creation, following the backend development guidelines. Include Zod validation and Sentry error tracking.

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 routes, controllers, services, and repositories into distinct concerns. This Skill enforces a standardized pattern where routes handle HTTP requests, controllers orchestrate logic, services contain business rules, and repositories manage data access via Prisma, improving testability and maintainability across your microservices.

How do I validate API request data with Zod in Express?

Zod validation ensures type-safe input handling at the route or controller layer. This Skill integrates Zod schemas to parse and validate incoming request payloads before they reach business logic, catching runtime errors early and providing clear error messages to API clients.

Can I use Sentry for error tracking and monitoring in Node.js microservices?

Yes, Sentry integrates seamlessly with Node.js/Express backends to capture exceptions, performance issues, and runtime errors automatically. This Skill implements centralized error handling with Sentry, ensuring all errors are tracked, logged with context, and surfaced for debugging without manual instrumentation.

What's the best way to organize TypeScript controllers and services in Express?

Controllers should delegate business logic to services and data access to repositories following dependency injection patterns. This Skill provides BaseController and standardized service patterns that enforce consistent organization across routes, controllers, services, and repositories, making TypeScript code predictable and reusable.

How do I manage type-safe configuration across Node.js microservices?

Type-safe configuration via unifiedConfig eliminates environment variable errors and inconsistencies. This Skill centralizes configuration management, validates it at startup with TypeScript types, and distributes it safely across services, preventing runtime failures from misconfigured deployments.

When should I apply backend development guidelines to existing Express projects?

Apply these guidelines when migrating legacy patterns, adding new API endpoints, or scaling microservices. This Skill handles both new features and migrations from inconsistent implementations, ensuring consistent error handling, validation, data access, and monitoring across your codebase regardless of starting point.