CtrlK
BlogDocsLog inGet started
Tessl Logo

jpc0/mim-architecture

Design, develop, and test software systems using the MIM (Module - Infrastructure - Module) architecture and foundational modular design principles.

100

1.25x
Quality

100%

Does it follow best practices?

Impact

100%

1.25x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Evaluation results

100%

30%

Battery Health Monitoring Scaffolding

Battery Monitoring Module Scaffolding (BM/IM split)

Criteria
Without context
With context

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%

100%

15%

Refactor User Registration for Maintainability

Refactoring to Vertical Modules (MIM)

Criteria
Without context
With context

Cohesive Feature Folder

100%

100%

MIM Folder Structure

50%

100%

Process-based Name

100%

100%

Zero IM imports in BM

100%

100%

100%

Secure Cross-Module Checkout

Cross-Module Communication via Public API

Criteria
Without context
With context

Service-to-Service interaction

100%

100%

No Repo Imports

100%

100%

No Model Imports

100%

100%

100%

Testing for Refactoring Safety

Sociable Unit Testing with Fakes

Criteria
Without context
With context

Sociable testing via Public API

100%

100%

Hand-written Fake usage

100%

100%

No automated mocking

100%

100%

State-based behavioral assertions

100%

100%

100%

55%

Complete the User Management Module

Infrastructure Implementation and Dependency Injection

Criteria
Without context
With context

IM/BM Folder Separation

0%

100%

IM depends on BM

50%

100%

DI Wiring outside BM

100%

100%

Strict BM Technical Isolation

50%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents