backend-dev-guidelines

Enforce layered Express and TypeScript backend architecture with Zod validation and Sentry error capture.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/gajjalaashok75-UI/GakrCLI --skill backend-dev-guidelines-gajjalaashok75-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-dev-guidelines
Source: https://github.com/gajjalaashok75-UI/GakrCLI/tree/main/assets/skills/backend-atlas/backend-dev-guidelines
Command: npx skills add https://github.com/gajjalaashok75-UI/GakrCLI --skill backend-dev-guidelines-gajjalaashok75-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill helps engineers design and implement backend features with predictable structure, strong validation, and reliable error handling so production services stay maintainable under real traffic.

Core Features & Use Cases

  • Layered architecture enforcement: Keeps routes, controllers, services, and repositories separated so business logic does not leak into HTTP handlers.
  • Validation and error discipline: Uses Zod input validation, centralized config, and Sentry-backed error handling to reduce runtime failures.
  • Database and service patterns: Guides Prisma repository usage, dependency injection, transactions, and testable service design for common backend workflows.
  • Use case: A team adding a new user-management API can use this Skill to structure the endpoint, validate input, query the database through a repository, and capture failures consistently.

Quick Start

Apply the backend-dev-guidelines skill to review this Express and Prisma feature for architecture, validation, error handling, and test coverage.

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 an Express backend with TypeScript to separate routes, controllers, and services?

Layered architecture enforcement separates routes, controllers, services, and repositories in Express and TypeScript services. This prevents business logic from leaking into HTTP handlers and maintains predictable service structure.

What is the best way to validate API request inputs in an Express application?

Zod input validation provides strong validation discipline for API requests. By applying Zod alongside centralized configuration, you reduce runtime failures and ensure predictable data structures across your backend services.

How do I implement Prisma database access patterns that support testable dependency injection?

Prisma repository usage guides database access patterns by implementing dependency injection and transactions. This approach ensures testable service design for common backend workflows while maintaining clear separation from business logic.

Does this backend architecture approach work with Sentry for centralized error handling?

Yes, this backend architecture approach integrates Sentry-backed error handling to capture failures consistently. Combined with Zod validation and unified configuration, it enforces error discipline to reduce runtime failures in production services.

When do I need dependency injection in a TypeScript backend service?

Dependency injection is needed when designing testable backend services with predictable structure. It enables isolated testing of business logic by injecting repository dependencies, ensuring services remain maintainable under real traffic.