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": "Use Endpoints/ folder with MapGet/MapPost for minimal API projects",
"relevant_when": "Agent builds a lightweight or small-scoped ASP.NET Core API that fits the minimal API pattern",
"context": "Minimal APIs use an Endpoints/ folder (not Controllers/) with static extension methods containing MapGet, MapPost, MapPut, MapDelete calls. Endpoint handlers delegate to service classes.",
"sources": [
{
"type": "file",
"filename": "skills/aspnet-project-structure/SKILL.md",
"tile": "tessl-labs/aspnet-project-structure@0.1.3"
}
],
"checklist": [
{
"name": "endpoints-not-controllers",
"rule": "Agent creates an Endpoints/ directory instead of a Controllers/ directory for minimal API projects",
"relevant_when": "Agent builds a lightweight ASP.NET Core minimal API"
},
{
"name": "map-methods-used",
"rule": "Agent uses MapGet, MapPost, MapPut, or MapDelete calls in endpoint files instead of [HttpGet]/[HttpPost] controller attributes",
"relevant_when": "Agent defines routes in a minimal API project"
},
{
"name": "endpoints-delegate-to-services",
"rule": "Agent delegates business logic from endpoint handlers to service classes, not inline in lambdas",
"relevant_when": "Agent implements endpoint handlers in a minimal API"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
aspnet-project-structure
verifiers