CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-unified-process/aiup-angular-jpa

AI Unified Process plugin for the Angular/JPA stack

92

0.99x
Quality

91%

Does it follow best practices?

Impact

99%

0.99x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Evaluation results

100%

Implement "Browse Product Catalog" (UC-010)

Implement backend + frontend for a use case (flat module, Angular/JPA)

Criteria
Baseline
With context

Product JPA entity created

100%

100%

Spring Data JPA repository created

100%

100%

Service class enforces BR-010

100%

100%

Controller returns a DTO, not the entity

100%

100%

REST endpoint exposed

100%

100%

Did not fabricate a hexagonal module split

100%

100%

Angular component uses signals

100%

100%

Standalone component, no NgModule

100%

100%

Hand-written HttpClient service

100%

100%

Category filter dropdown in the UI

100%

100%

No test files created

100%

100%

100%

Implement "Register Guest" (UC-020) in a Hexagonal Multi-Module Backend

Hexagonal-aware /implement: add a new feature matching an existing multi-module exemplar

Criteria
Baseline
With context

Pure domain record with zero framework imports

100%

100%

No JPA/Spring leakage into hotel-domain

100%

100%

Outbound port as plain sibling interface, not a port subpackage

100%

100%

No inbound port/use-case interface invented

100%

100%

Controller depends on the concrete service

100%

100%

DTO factory method on the DTO record itself

100%

100%

Hand-written static converters, not MapStruct

100%

100%

Separate JPA entity from the domain record

100%

100%

Spring Data repository + port implementation in hotel-postgres

100%

100%

Flyway migration placed in the persistence-adapter module

100%

100%

Email uniqueness enforced at the database level

100%

100%

Correct module for each new file

100%

100%

No test files created

100%

100%

98%

-2%

Write Backend Tests for "Register Guest" (UC-020)

spring-boot-test convention detection: RestAssured/Testcontainers vs MockMvc

Criteria
Baseline
With context

Test class name pattern

100%

87%

Extends IntegrationTestBase

100%

100%

Uses RestAssured, not MockMvc/MockMvcTester/RestTestClient

100%

100%

Reuses the existing UseCase annotation

100%

100%

@UseCase on every test method

100%

100%

@UseCase scenario matches spec

100%

100%

@UseCase businessRules matches spec

100%

100%

Main scenario test present

100%

100%

Duplicate-email test present

100%

100%

No repository/service mocking

100%

100%

Cleanup via JdbcTemplate, not a separate test migration

100%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents