What problem does it solve?
Prevents long-term bugs, security vulnerabilities, and maintenance debt by identifying common coding anti-patterns early in the development lifecycle. It targets issues that slip into production when frontend data is trusted, validation is missing, business logic is mixed into UI, or secrets and unsafe types are introduced.
Core Features & Use Cases
- Server-side validation enforcement: Emphasizes validating frontend inputs on the server to prevent privilege escalation and data corruption.
- Separation of concerns: Encourages extracting logic from UI components into hooks and services to improve testability and reuse.
- Type safety and duplication reduction: Recommends replacing any with explicit types or unknown+validation and extracting shared UI/code to avoid drift.
- Secrets and deployment safety: Calls out hardcoded secrets and NEXT_PUBLIC exposure, and checks for functional placeholders shipped to users.
- Use Case: Run this as part of PR reviews or before releases to produce a checklist of fixes (validation schemas, service layers, typed interfaces, and secrets audit).
Quick Start
Run the anti-patterns checklist on your codebase or pull request and list each violation with a suggested fix and the priority to address it.
