ASP.NET Core project structure — minimal APIs vs controllers, layer
95
93%
Does it follow best practices?
Impact
100%
2.50xAverage score across 5 eval scenarios
Passed
No known issues
{
"instruction": "Store all configuration in appsettings.json with environment overrides",
"relevant_when": "Agent configures an ASP.NET Core application with connection strings or app settings",
"context": "Configuration must live in appsettings.json (not hardcoded in Program.cs). Connection strings go in ConnectionStrings section. Environment-specific overrides go in appsettings.Development.json. Health checks should be registered.",
"sources": [
{
"type": "file",
"filename": "skills/aspnet-project-structure/SKILL.md",
"tile": "tessl-labs/aspnet-project-structure@0.1.3"
}
],
"checklist": [
{
"name": "config-in-appsettings",
"rule": "Agent stores connection strings and app settings in appsettings.json, not hardcoded in Program.cs or other C# files",
"relevant_when": "Agent configures database connections or application settings"
},
{
"name": "environment-overrides",
"rule": "Agent creates appsettings.Development.json for development-specific configuration overrides",
"relevant_when": "Agent sets up configuration for an ASP.NET Core project"
},
{
"name": "health-checks-registered",
"rule": "Agent registers health checks with AddHealthChecks() and maps them to /health endpoint",
"relevant_when": "Agent builds a production-ready ASP.NET Core API"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
aspnet-project-structure
verifiers