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": "Use multi-profile application.yml with separate dev/prod/test configurations",
"relevant_when": "Agent configures a Spring Boot application with application.yml or application.properties",
"context": "Spring Boot applications should have a base application.yml with shared defaults plus profile-specific files (application-dev.yml, application-prod.yml, application-test.yml). Key settings: spring.jpa.open-in-view should be false, server.shutdown should be graceful, datasource and logging levels should vary by profile. Never hardcode environment-specific values in the base file — use ${ENV_VAR:default} placeholders.",
"sources": [
{
"type": "file",
"filename": "skills/springboot-project-structure/SKILL.md",
"tile": "tessl-labs/springboot-project-structure@0.2.0"
}
],
"checklist": [
{
"name": "profile-files-exist",
"rule": "At least two profile-specific configuration files exist (e.g., application-dev.yml and application-prod.yml) in addition to the base application.yml",
"relevant_when": "Agent creates a Spring Boot application with configuration files"
},
{
"name": "osiv-disabled",
"rule": "spring.jpa.open-in-view is set to false in the base or production configuration",
"relevant_when": "Agent configures JPA in a Spring Boot application"
},
{
"name": "graceful-shutdown",
"rule": "server.shutdown is set to graceful",
"relevant_when": "Agent configures a Spring Boot application for production readiness"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers