Spring Boot project structure — package-by-feature, record DTOs, Flyway migrations, multi-profile config, actuator, proper test structure
84
76%
Does it follow best practices?
Impact
97%
4.04xAverage score across 5 eval scenarios
Passed
No known issues
Build the backend API for a simple blog platform using Spring Boot 3 and Java 17+.
Domain concepts:
Endpoints:
POST /api/authors -- create an authorGET /api/authors/:id -- get author with their published post countPOST /api/posts -- create a post (starts as DRAFT, slug auto-generated from title)GET /api/posts -- list published posts with pagination (page, size params), ordered by publishedAt descGET /api/posts/:slug -- get a single published post by slug, including author info and approved commentsPATCH /api/posts/:id/publish -- change post status to PUBLISHED and set publishedAtPOST /api/posts/:id/comments -- add a comment (commenterName and body required, starts as approved=false)PATCH /api/comments/:id/approve -- approve a commentBusiness rules:
Use PostgreSQL for the database.
Produce a complete Spring Boot project with:
pom.xml with dependenciesYou may create additional files as needed.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers