ai-unified-process/aiup-nestjs-nextjs
AI Unified Process plugin for the NestJS/Drizzle + Next.js stack
92
91%
Does it follow best practices?
Impact
97%
1.15xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Evaluation results
100%
Add the Supplier entity to the schema
Add an entity and change a field via the Drizzle schema and a generated migration
Schema edited, not SQL hand-written
100%
100%
Applied migration left untouched
100%
100%
New migration added
100%
100%
Journal kept in sync
100%
100%
Correct pg-core types
100%
100%
country_code constraint expressed in the schema
100%
100%
Optional relationship modelled correctly
100%
100%
snake_case column naming
100%
100%
99%
6%Implement "Browse Product Catalog" (UC-010)
Implement backend + frontend for a use case (NestJS/Drizzle + Next.js)
Feature module created with the full anatomy
100%
100%
Repository owns all database access
100%
100%
Service enforces BR-010
100%
100%
Controller returns a response DTO, not a raw row
100%
100%
ESM .js import suffixes
100%
100%
Module registered in app.module.ts
100%
100%
Query parameter validated by a DTO
0%
100%
Frontend page implemented at the existing route
100%
100%
Relative /api path, no hardcoded origin
100%
100%
Category filter control rendered
100%
80%
No test files created
100%
100%
92%
33%Test the product catalogue feature (UC-010)
Write unit and e2e tests for an implemented NestJS feature
unplugin-swc added to the Vitest config
0%
100%
Oxc interaction addressed
0%
0%
Unit spec with a stubbed repository
64%
100%
e2e spec boots the app with Supertest
100%
100%
Testcontainers PostgreSQL, not a mock
100%
100%
One shared container, reset per file
30%
100%
App lifecycle in beforeAll/afterAll
100%
100%
BR-010 covered
100%
100%
Alternative flow A1 covered
100%
100%
Use case traceability in test names
50%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6