backend-dev-guidelines

Standardize Node.js/Express/TypeScript microservices with layered architecture and naming conventions.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill backend-dev-guidelines-jokken79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/jokken79/YuKyuDATA-app1.0v/tree/main/.agent/skills/backend-dev-guidelines
Command: npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill backend-dev-guidelines-jokken79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend teams often grapple with inconsistent architectures across services, leading to duplicated boilerplate and slow onboarding.

Core Features & Use Cases

  • Layered architecture blueprint (routes → controllers → services → repositories)
  • Standardized naming conventions, project structure, and error handling with Sentry
  • Guidance on validation (Zod), testing strategies, and migration from legacy patterns

Quick Start

Review the architecture overview and implement the prescribed folder structure and patterns in your Node.js/Express/TypeScript backend project.

Frequently Asked Questions about backend-dev-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to structure a Node.js Express TypeScript backend?

Standardize your Node.js Express TypeScript backend using a layered architecture: routes call controllers, controllers call services, and services call repositories. This blueprint ensures maintainable code and consistent folder structures across microservices.

How do I standardize error handling and Sentry integration across microservices?

Standardize error handling across Node.js microservices by implementing a unified error handling pattern with Sentry integration. This ensures consistent error catching and reporting, making your backend services fully observable during runtime.

Does this backend architecture blueprint support Prisma and Zod validation?

Yes, the backend architecture blueprint supports Prisma and Zod validation. It provides specific guidance on implementing Zod for request validation and structuring your data access layer around Prisma within the repository pattern.

How do I migrate legacy backend patterns to a layered architecture?

Migrate legacy backend code by adopting the prescribed folder structure and layered architecture blueprint. Refactor monolithic route logic into distinct controllers, services, and repositories to establish consistent naming conventions and maintainable code.

What testing strategies should I use for Express TypeScript microservices?

Apply testing strategies that align with the layered architecture for your Express TypeScript microservices. The blueprint provides specific testing guidance to validate routes, controllers, services, and repositories consistently across your project.