backend-dev-guidelines

Enforce layered architecture and coding standards for Node.js/Express/TypeScript microservices.

Updated Nov 3, 2025
One-click install
npx skills add https://github.com/duckviet/njs-go-penapi-cci --skill backend-dev-guidelines-duckviet
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/duckviet/njs-go-penapi-cci/tree/main/.claude/skills/backend-dev-guidelines
Command: npx skills add https://github.com/duckviet/njs-go-penapi-cci --skill backend-dev-guidelines-duckviet

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes backend development for Node.js/Express/TypeScript microservices, eliminating inconsistencies, improving error handling, and ensuring scalable, maintainable code. It automates the process of applying best practices, allowing developers to focus on business logic rather than boilerplate.

Core Features & Use Cases

  • Layered Architecture: Enforces clear separation of concerns (routes β†’ controllers β†’ services β†’ repositories) for modularity and easier maintenance.
  • Automated Error Tracking: Integrates Sentry for comprehensive error monitoring and reporting, reducing manual debugging and improving system reliability.
  • Robust Input Validation: Utilizes Zod for type-safe schema validation, preventing common API errors and enhancing data integrity.
  • Use Case: When building a new API endpoint, activate this Skill to automatically generate the correct file structure, apply Zod validation, set up Sentry tracking, and ensure adherence to the BaseController pattern, saving hours of setup and code review.

Quick Start

To create a new backend feature, follow the "New Backend Feature Checklist" in the backend-dev-guidelines skill. For example, to create a new route with validation: 1. Define a Zod schema in validators/. 2. Create a service in services/ for business logic. 3. Implement a controller in controllers/ extending BaseController. 4. Define the route in routes/ delegating to the controller.

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 API with layered architecture?β–Ό

Layered architecture separates routes, controllers, services, and repositories into distinct folders to improve modularity and maintainability. This Skill enforces that pattern across your Express application, ensuring consistent code organization that makes testing and debugging easier.

What's the best way to validate API input in TypeScript with Express?β–Ό

Use Zod schemas to define and validate request data types at your API boundaries. This Skill integrates Zod validation into controllers automatically, catching data errors before they reach your business logic and preventing type mismatches.

How do I set up error tracking and monitoring for Node.js microservices?β–Ό

Integrate Sentry to capture, log, and alert on errors across your Express services in real time. This Skill configures Sentry instrumentation in your controllers and middleware, giving you visibility into failures without manual debugging.

Can I use Prisma for database access in a layered Express architecture?β–Ό

Yes. Prisma integrates into the repository layer of this architecture, providing type-safe database queries. This Skill includes patterns and templates for connecting Prisma repositories to your services and controllers.

How do I enforce consistent backend patterns across a team's microservices?β–Ό

Apply this Skill when scaffolding new features or auditing existing code. It delivers checklists, BaseController patterns, and code templates that standardize dependency injection, validation, error handling, and middleware across your Node.js services.