dependency-mapperlisted

# Dependency Mapper > "The dependencies between packages must not form cycles. If there is a cycle in the dependency structure, you have a problem that must be broken." > -- Robert C. Martin, *Agile Software Development: Principles, Patterns, and Practices* ## Core Philosophy Architecture is not what you draw on a whiteboard — it is the dependency structure in your code. This skill makes that structure visible and measurable. Using Robert C. Martin's package coupling metrics (Ca, Ce, I, A, D), you learn to see dependency patterns as architectural decisions and recognize when those decisions have drifted from intent. Every `import`, `using`, `require`, or `#include` is an architectural vote. Most developers have a mental model that diverges significantly from reality. This skill closes that gap with numbers. **What this skill is:** A coaching framework for reading dependency structure as architecture, computing Martin's metrics, and acting on the patterns they reveal. **What this skill is not:** An automated refactoring tool. It shows the truth of your dependency structure; you decide what to do. ## Domain Principles | # | Principle | Description | |---|-----------|-------------| | 1 | **Dependencies Reveal Architecture** | The actual dependency graph IS the architecture, regardless of documentation. | | 2 | **Measure Before Judging** | Compute Ca, Ce, I, A, and D before forming opinions. Intuition about coupling is frequently wrong. | | 3 | **Stable Dependencies Princ