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
Battery Monitoring Module Scaffolding (BM/IM split)
Feature-centric Folder
100%
100%
MIM naming convention
0%
100%
Strict BM isolation
75%
100%
BM-defined Interfaces
100%
100%
IM-implemented Adapters
75%
100%
Without context: $0.6336 · 2m 42s · 33 turns · 37 in / 9,654 out tokens
With context: $0.8056 · 2m 45s · 38 turns · 1,918 in / 10,518 out tokens
Refactoring to Vertical Modules (MIM)
Cohesive Feature Folder
100%
100%
MIM Folder Structure
50%
100%
Process-based Name
100%
100%
Zero IM imports in BM
100%
100%
Without context: $0.3662 · 1m 25s · 22 turns · 27 in / 4,579 out tokens
With context: $0.6782 · 2m 19s · 36 turns · 792 in / 7,302 out tokens
Cross-Module Communication via Public API
Service-to-Service interaction
100%
100%
No Repo Imports
100%
100%
No Model Imports
100%
100%
Without context: $0.5589 · 2m 33s · 30 turns · 37 in / 7,583 out tokens
With context: $0.5832 · 2m 13s · 30 turns · 787 in / 6,949 out tokens
Sociable Unit Testing with Fakes
Sociable testing via Public API
100%
100%
Hand-written Fake usage
100%
100%
No automated mocking
100%
100%
State-based behavioral assertions
100%
100%
Without context: $0.2894 · 1m 31s · 16 turns · 18 in / 4,380 out tokens
With context: $0.6422 · 2m 14s · 32 turns · 901 in / 7,963 out tokens
Infrastructure Implementation and Dependency Injection
IM/BM Folder Separation
0%
100%
IM depends on BM
50%
100%
DI Wiring outside BM
100%
100%
Strict BM Technical Isolation
50%
100%
Without context: $0.4499 · 1m 59s · 28 turns · 35 in / 5,953 out tokens
With context: $0.7085 · 2m 20s · 37 turns · 1,032 in / 8,118 out tokens
Install with Tessl CLI
npx tessl i jpc0/mim-architecture