NestJS architecture, dependency injection, validation, security, errors, testing, persistence, APIs, microservices, and deployment patterns with prioritized rule tiers and companion rule files.
99
100%
Does it follow best practices?
Impact
97%
1.12xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
This file defines all sections, their ordering, impact levels, and descriptions. The section ID (in parentheses) is the filename prefix used to group rules.
Impact: CRITICAL Description: Proper module organization and dependency management are the foundation of maintainable NestJS applications. Circular dependencies and god services are the #1 architecture killer.
Impact: CRITICAL Description: NestJS's IoC container is powerful but can be misused. Understanding scopes, injection tokens, and proper patterns is essential for testable code.
Impact: HIGH Description: Consistent error handling improves debugging, user experience, and API reliability. Centralized exception filters ensure uniform error responses.
Impact: HIGH Description: Security vulnerabilities can be catastrophic. Input validation, authentication, authorization, and data protection are non-negotiable.
Impact: HIGH Description: Optimizing request handling, caching, and database queries directly impacts application responsiveness and scalability.
Impact: MEDIUM-HIGH Description: Well-tested applications are more reliable. NestJS testing utilities enable comprehensive unit and e2e coverage.
Impact: MEDIUM-HIGH Description: Proper database access patterns, transactions, and query optimization are crucial for data-intensive applications.
Impact: MEDIUM Description: RESTful conventions, versioning, DTOs, and consistent response formats improve API usability and maintainability.
Impact: MEDIUM Description: Building distributed systems requires understanding message patterns, health checks, and inter-service communication.
Impact: LOW-MEDIUM Description: Configuration management, structured logging, and graceful shutdown ensure production readiness and zero-downtime deployments.
evals
scenario-1
scenario-2
rules