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 Flyway or Liquibase for database schema management, not ddl-auto or schema.sql",
"relevant_when": "Agent creates database tables or schema in a Spring Boot application",
"context": "Production Spring Boot applications must use a proper migration tool (Flyway or Liquibase) for database schema management. hibernate.ddl-auto should be 'validate' in production (never 'update' or 'create'). schema.sql and data.sql are acceptable only for prototypes. Migration files follow the naming convention V{number}__{description}.sql and are immutable once applied.",
"sources": [
{
"type": "file",
"filename": "skills/springboot-project-structure/SKILL.md",
"tile": "tessl-labs/springboot-project-structure@0.2.0"
}
],
"checklist": [
{
"name": "migration-tool-used",
"rule": "Flyway or Liquibase dependency is included and migration files exist in db/migration/ (Flyway) or db/changelog/ (Liquibase)",
"relevant_when": "Agent creates a Spring Boot application with a database"
},
{
"name": "ddl-auto-validate-or-none",
"rule": "spring.jpa.hibernate.ddl-auto is set to 'validate' or 'none' in production configuration. 'create-drop' or 'create' is acceptable only in dev/test profiles.",
"relevant_when": "Agent configures Hibernate ddl-auto in a Spring Boot application"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers