Create standardized HTTP controllers for the zoppy-api project.
npx skills add https://github.com/Zoppy-crm/.github --skill controller-zoppy-crm
Please help me install this Agent Skill. Skill: controller Source: https://github.com/Zoppy-crm/.github/tree/main/skills/backend/controller Command: npx skills add https://github.com/Zoppy-crm/.github --skill controller-zoppy-crm
Provides a clear, organization-wide pattern for implementing HTTP controllers in the zoppy-api project so that controllers remain thin, consistent, and free of business logic while ensuring security, transaction safety, and predictable request/response contracts.
Create a new NestJS controller that exposes CRUD endpoints, applies BlockFreeTierGuard and RoleGuard on protected routes, uses UsingTransaction for write operations and ExceptionInterceptor for all endpoints, defines request and response DTOs, and register the controller in the HttpModule.
High-intent search queries and answers about installing and using this skill.
To create consistent NestJS controllers, apply thin-controller patterns that delegate business logic to Application Services while using guards like RoleGuard, BlockFreeTierGuard, and decorators such as UsingTransaction and ExceptionInterceptor for security and transaction safety.
The thin-controller pattern keeps HTTP controllers free of business logic by delegating rules to Application Services, ensuring predictable request and response contracts while enforcing security, feature flags, and transaction safety across REST endpoints.
Configure rate limiting and role-based access by applying the RateLimit decorator and RoleGuard to protected routes, combining them with BlockFreeTierGuard and FeatureGuard to enforce security policies and feature flags on your NestJS controllers.
Yes, the pattern supports multipart file handling and defines explicit request and response DTO conventions, ensuring consistent routing and integration testing readiness when registering controllers in the HttpModule.
HTTP controllers leak domain logic when business rules are written directly in endpoint handlers; preventing this requires delegating all logic to Application Services and using standardized decorators like UsingTransaction and ExceptionInterceptor to maintain separation.
You should never place business logic inside a NestJS controller when following the thin-controller pattern; controllers must only handle HTTP concerns, routing, and decorator configuration while Application Services manage all domain rules and transactions.
luongldptitStandardize modular NestJS TypeScript backend patterns with DTO validation and error handling.
jakubciszakDesign REST APIs for Symfony backends with OpenAPI specifications and DTO-based contracts.
Zoppy-crmIdentify architecture, security, PII, and performance issues in NestJS code.
ngxtmEnforce NestJS architectural patterns for controllers, services, DTOs, and validation.
