Design, develop, and test software systems using the MIM (Module - Infrastructure - Module) architecture and foundational modular design principles.
100
Quality
100%
Does it follow best practices?
Impact
100%
1.25xAverage score across 5 eval scenarios
{
"context": "Evaluates the ability to scaffold a new module according to MIM principles, specifically checking for vertical organization, BM/IM split, and dependency inversion via interfaces.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Feature-centric Folder",
"description": "All files for the BatteryMonitoring feature are contained within a single top-level feature-specific directory (not split across global layers).",
"max_score": 20
},
{
"name": "MIM naming convention",
"description": "The module contains sub-folders or namespaces explicitly named 'BM' (Business-Module) and 'IM' (Infrastructure-Module).",
"max_score": 20
},
{
"name": "Strict BM isolation",
"description": "The 'BM' section contains ZERO imports of technical infrastructure such as database drivers (SQL, Prisma, etc.) or network frameworks.",
"max_score": 20
},
{
"name": "BM-defined Interfaces",
"description": "The Business-Module defines at least one public interface (Port) for required external actions like persistence or alerting.",
"max_score": 20
},
{
"name": "IM-implemented Adapters",
"description": "The Infrastructure-Module contains concrete implementations of the interfaces defined in the BM.",
"max_score": 20
}
]
}