coupling-analysis

Identify coupling issues across system components with a five-dimension analysis.

1|Updated Jan 13, 2023
One-click install
npx skills add https://github.com/theodrosyimer/.dotfiles --skill coupling-analysis-theodrosyimer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coupling-analysis
Source: https://github.com/theodrosyimer/.dotfiles/tree/main/claude/skills/arch__coupling-analysis
Command: npx skills add https://github.com/theodrosyimer/.dotfiles --skill coupling-analysis-theodrosyimer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps architects and engineers uncover hidden dependencies and evaluate them across operational, development, semantic, functional, and incidental dimensions, ensuring informed decisions when adding or modifying integrations.

Core Features & Use Cases

  • Framework‑driven analysis: Reads a five‑dimension coupling framework before any assessment.
  • Automated context discovery: Inspects the project’s stack (package.json) and architecture documentation to ground the analysis.
  • Coupling matrix generation: Rates each outbound dependency (Strong, Moderate, Weak) on all five dimensions with concise justification.
  • Anti‑pattern detection: Flags semantic polymers, long arrows, shared DB coupling, and latent incidental issues.
  • Tailored recommendations: Provides concrete, stack‑aware strategies and trade‑offs for each weak or moderate rating.

Quick Start

Ask Claude to perform a coupling analysis on the booking module by providing its name.

Frequently Asked Questions about coupling-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a five-dimensional coupling analysis for software architecture?

A five-dimensional coupling analysis evaluates system dependencies across operational, development, semantic, functional, and incidental dimensions. It generates a coupling matrix that rates each outbound dependency to uncover hidden integration issues and inform architectural decisions.

How do I analyze module boundaries and external integrations for hidden dependencies?

You can analyze module boundaries by applying a structured coupling matrix to rate each outbound dependency as Strong, Moderate, or Weak. The framework inspects your project stack and architecture documentation to ground the dependency assessment.

Can I detect architectural anti-patterns like shared database coupling and semantic polymers?

Yes, coupling analysis detects anti-patterns including semantic polymers, long arrows, shared DB coupling, and latent incidental issues. It flags these dependencies during the matrix generation to highlight problematic integrations.

Does this coupling analysis framework support Node.js projects?

The framework supports Node.js projects by automatically inspecting the package.json file to discover your project stack. This automated context discovery grounds the five-dimensional analysis in your specific technology stack.

What is the best way to get stack-aware recommendations for weak or moderate system dependencies?

The best way is to generate a coupling matrix that rates dependencies across five dimensions and provides concrete, stack-aware strategies. It delivers tailored recommendations with specific trade-offs for each weak or moderate rating.

When should I not use a coupling matrix for system architecture evaluation?

A coupling matrix may be unnecessary for simple systems with minimal outbound dependencies or isolated slices with no external integrations. It is designed for complex module boundaries and integration points requiring multi-dimensional evaluation.