What is the Balanced Coupling Model used by this skill?

It is a framework from Vlad Khononov that defines modularity by balancing integration strength against physical distance, while accounting for the volatility of the components involved.

How does this skill help identify a 'distributed monolith'?

It flags 'Complexity' errors where components have high integration strength (like shared business logic or direct database access) but are located at a high distance from each other, such as in different microservices.

Can I use this tool for both monoliths and microservices?

Yes, the evaluator scales across different 'distances,' meaning it can analyze coupling within a single file, between packages in a monolith, or across independent services in a distributed system.

What is the difference between static and dynamic connascence in its analysis?

Static connascence refers to coupling detectable at compile-time (like shared names or types), while dynamic connascence refers to runtime dependencies (like execution order or timing) which are often harder to refactor.

Code Modularization Evaluator

Name: Code Modularization Evaluator
Author: dotneet

bydotneet

Collaboration Tools

Analyzes and optimizes software architecture using the Balanced Coupling Model to reduce technical debt and improve system maintainability.

About

The Code Modularization Evaluator is a sophisticated architectural analysis tool for Claude Code that applies the principles of the Balanced Coupling Model and connascence theory. It systematically evaluates the relationships between software components across three dimensions—integration strength, distance, and volatility—to identify architectural risks like 'distributed monoliths' and over-engineered abstractions. By providing actionable refactoring guidance based on the modularity formula, it helps developers transition from fragile, high-coupling code to resilient, modular systems that are easier to scale and maintain.

Key Features

Distributed monolith detection and resolution strategies
Static and Dynamic connascence type identification
0 GitHub stars
Integration strength assessment across module boundaries
Automated Balanced Coupling Model analysis
Structured architectural health reports with prioritized refactoring plans

Use Cases

Evaluating the impact of proposed changes on system coupling and modularity
Performing deep architectural reviews during major refactoring sessions
Identifying and fixing 'leaky abstractions' and circular dependencies in microservices

About

Key Features

Distributed monolith detection and resolution strategies
Static and Dynamic connascence type identification
0 GitHub stars
Integration strength assessment across module boundaries
Automated Balanced Coupling Model analysis
Structured architectural health reports with prioritized refactoring plans

Use Cases

Evaluating the impact of proposed changes on system coupling and modularity
Performing deep architectural reviews during major refactoring sessions
Identifying and fixing 'leaky abstractions' and circular dependencies in microservices