Coupling Analysis
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
Install
/plugin marketplace add tech-leads-club/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tech-leads-club/agent-skills --skill coupling-analysisgit clone --depth 1 https://github.com/tech-leads-club/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/packages/skills-catalog/skills/(architecture)/coupling-analysis ~/.claude/skills/coupling-analysisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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): 1. **Integration Strength** — _what_ is shared between components 2. **Distance** — _where_ the coupling physically lives 3. **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 ## When to Use Apply this skill when the user: - Asks to "analyze coupling", "evaluate architecture", or "check dependencies" - Wants to understand integration strength between modules or services - Needs to identify problematic coupling or architectural smell - Wants to know if a module should be extracted or merged - References concepts like connascence, cohesion, or coupling from Khononov's book - Asks why changes in one module cascade to others unexpectedly ## Process ### PHASE 1 — Context Gathering Before analyzing code, collect: **1.1 Scope** - Full codebase or a specific area? - Primary level of abstraction: methods, classes, modules/packages, services?
Details
- Skill name
coupling-analysis- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(architecture)/coupling-analysis/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Coupling Analysis skill do?
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
How do I install the Coupling Analysis skill?
Claude Code plugin: /plugin marketplace add tech-leads-club/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Coupling Analysis popular?
It lives in tech-leads-club/agent-skills, which has 7,177 GitHub stars and 568 forks.
Related skills
Frontend Design
7.2ktech-leads-club/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit).
Web Design Guidelines
7.2ktech-leads-club/agent-skills
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).
AI Cold Outreach
7.2ktech-leads-club/agent-skills
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
Domain Analysis
7.2ktech-leads-club/agent-skills
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).
Confluence Assistant
7.2ktech-leads-club/agent-skills
Expert in Confluence operations using Atlassian MCP. Use when the user says "search Confluence", "create a Confluence page", "update a page", "find documentation in Confluence", "list spaces", or "add a comment to a page". Do NOT use for Jira issues, general web search, or local file creation.
Domain Identification Grouping
7.2ktech-leads-club/agent-skills
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.