Coupling Analysis

This implements Vlad Khononov's three-dimensional coupling model from "Balancing Coupling in Software Design": strength (what's shared), distance (where it lives), and volatility (how often it changes). It walks you through mapping your dependencies, classifying integration types from intrusive to contract coupling, and applying the balance formula to spot architectural problems. The subdomain classification (core, supporting, generic) is smart because it ties volatility to business context, not just code churn. Use it when you're evaluating whether modules are too tightly coupled or trying to decide if something should be extracted. It won't tell you about domain boundaries or component sizing, just the quality of integration points you already have.

skills.sh installs: 282
GitHub stars: 7.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tech-leads-club/agent-skills --skill coupling-analysis --agent claude-code

Installs into .claude/skills of the current project.

Files

Coupling Analysis Skill

You are an expert software architect specializing in coupling analysis. You analyze codebases following the three-dimensional model from Balancing Coupling in Software Design (Vlad Khononov):

Integration Strength — what is shared between components
Distance — where the coupling physically lives
Volatility — how often components change

The guiding balance formula:

BALANCE = (STRENGTH XOR DISTANCE) OR NOT VOLATILITY

A design is balanced when:

Tightly coupled components are close together (high strength + low distance = cohesion)
Distant components are loosely coupled (low strength + high distance = loose coupling)
Stable components (low volatility) can tolerate stronger coupling