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.

Install to Claude Code

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