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
{
"instruction": "Place all @Configuration classes in a dedicated config/ package",
"relevant_when": "Agent creates @Configuration classes in a Spring Boot application",
"context": "Spring Boot @Configuration classes (SecurityConfig, WebConfig, JacksonConfig, AsyncConfig, etc.) configure cross-cutting infrastructure and should live in a dedicated config/ package at the top level, not scattered across feature packages. This makes it easy to find and audit all configuration in one place.",
"sources": [
{
"type": "file",
"filename": "skills/springboot-project-structure/SKILL.md",
"tile": "tessl-labs/springboot-project-structure@0.2.0"
}
],
"checklist": [
{
"name": "config-package-exists",
"rule": "A config/ package exists containing @Configuration classes for security, web, Jackson, or other cross-cutting concerns",
"relevant_when": "Agent creates a Spring Boot application with configuration beyond application.yml"
},
{
"name": "no-scattered-config",
"rule": "@Configuration classes are not placed inside feature packages or in the root application package",
"relevant_when": "Agent creates multiple @Configuration classes"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers