nestjs-backend

Name: nestjs-backend
Availability: InStock
Author: Kauanphbbb

Organize NestJS backend code into modules and repositories under apps/api/src.

Updated Aug 27, 2026

Search Tags:#typescript #architecture #backend #nestjs #typeorm #repository-pattern

Ready to run

npx skills add https://github.com/Kauanphbbb/my-schedule --skill nestjs-backend-kauanphbbb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nestjs-backend
Source: https://github.com/Kauanphbbb/my-schedule/tree/main/skills/nestjs-backend
Command: npx skills add https://github.com/Kauanphbbb/my-schedule --skill nestjs-backend-kauanphbbb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill to standardize and guide the development of backend code in the my-schedule project, ensuring consistent structure and patterns across modules, repositories, DTOs, entities, guards, and services.

Core Features & Use Cases

Enforces a uniform NestJS module layout under apps/api/src/modules/<feature>/ with clearly separated concerns (controller, service, repository, entities, dto).
Provides a dual-authentication and role-based access framework examples, including platform vs tenant guards, and JWT payload shapes.
Guides consistent entity modeling, repository patterns, and DTO usage for predictable, scalable backend development.

Quick Start

Implement a new feature by following the defined module structure and repository pattern in apps/api/src/modules/.

Frequently Asked Questions about nestjs-backend

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

FAQPage Schema

How do I structure a NestJS backend with TypeORM using the repository pattern?▼

To structure a NestJS backend with the repository pattern, organize code under modules/<feature>/ with strict separation of concerns between controllers, services, and custom TypeORM repositories. This ensures predictable, scalable backend development with explicit typing and snake_case database columns.

What is the best way to standardize NestJS module layout and DTOs in a TypeScript project?▼

The best way to standardize a NestJS module layout is to enforce a uniform directory structure under apps/api/src/modules/<feature>/ with clearly separated concerns. This includes consistent entity modeling, explicit DTO usage, and explicit naming conventions across all generated files.

Does this NestJS backend standardization approach support role-based access control?▼

Yes, this NestJS backend standardization approach supports role-based access control by providing a dual-authentication framework. It includes platform versus tenant guards and defines JWT payload shapes to manage access securely across different modules.

How do I enforce separation of concerns when creating NestJS controllers and services?▼

To enforce separation of concerns in NestJS, apply a strict module pattern that isolates controllers for routing, services for business logic, and repositories for database operations. This architecture prevents logic overlap and maintains scalable code.

Can I use snake_case database columns with TypeORM entities in a NestJS application?▼

Yes, you can use snake_case database columns with TypeORM entities in a NestJS application. The standardization enforces consistent entity modeling with explicit typing and snake_case naming for database columns to ensure predictable data mapping.