What is the main goal of the tight coupling skill?

The primary goal is to help developers distinguish between acceptable, high-performance coupling and problematic architectural debt that makes codebases brittle and difficult to change.

How does this skill measure code coupling?

It utilizes metrics like Afferent (Ca) and Efferent (Ce) coupling, instability ratings (I), and git change history analysis to quantify how components depend on one another.

Which refactoring patterns does it recommend?

Depending on the coupling type, it suggests patterns such as Dependency Injection, Strategy, Builder, and Interface extraction to break direct dependencies.

Is tight coupling always considered a bad practice?

No; tight coupling is a deliberate trade-off. It can be appropriate for performance-critical code paths, internal implementation details, or rapid prototyping where speed outweighs long-term flexibility.

Architectural Coupling Management

Name: Architectural Coupling Management
Author: lev-os

bylev-os

0•

개발자 도구

Analyzes and remediates excessive interdependence between software components to improve maintainability and reduce architectural debt.

This skill empowers developers to identify and address problematic tight coupling within software systems by providing a structured framework for diagnosing various coupling types—such as stamp, control, and content coupling. It offers guidance on quantitative metrics like instability and connascence to justify refactoring efforts and prevent architectural rot. By applying industry-standard patterns like dependency injection and the strategy pattern, the skill helps teams balance the trade-offs between performance-driven interdependence and the flexibility required for independent component evolution.

주요 기능

01Provides targeted refactoring patterns including Dependency Injection and Strategy

02Calculates stability and instability metrics (Ca/Ce) for architectural health

03Establishes architectural governance rules using fitness functions and budgets

04Diagnoses six distinct coupling types ranging from data to content coupling

05Analyzes git history to identify hidden change coupling between unrelated files

060 GitHub stars

사용 사례

01Evaluating the long-term technical debt impact of new feature implementations

02Refactoring legacy monolithic systems into modular or microservices architectures

03Resolving circular dependencies and 'spaghetti code' in complex codebases

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lev-os/agents tight-coupling

For use in Claude.ai and ChatGPT

Download Skill