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
A warehouse team needs a small internal service to track product inventory. The service is intentionally narrow in scope -- it only handles three things: looking up current stock for a product, recording stock adjustments (received shipments or items shipped out), and listing low-stock alerts.
The team wants to keep it lean since it's an internal tool consumed by other services via JSON API. There's no separate frontend. The service uses ASP.NET Core with Entity Framework Core and SQLite.
The database connection should come from configuration files. The warehouse manager wants configurable thresholds for what counts as "low stock" (default: 10 units).
Produce the project under a directory called InventoryService/. Each file should contain valid C# skeletons (namespaces, class declarations, method signatures). Full implementation is not required, but the structure should be complete and files should be syntactically correct.
Include a project-structure.txt file at the root listing the directory tree.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
aspnet-project-structure
verifiers