package-principles

What problem does it solve?

This skill helps teams identify when packages or modules are organized in ways that increase maintenance cost, create dependency cycles, or force consumers to depend on unrelated classes. It highlights violations of REP, CCP, CRP (cohesion) and ADP, SDP, SAP (coupling) so maintainers can prioritize targeted refactors and safer releases.

Core Features & Use Cases

• Principle-based analysis: Evaluates packages against REP, CCP, CRP, ADP, SDP and SAP and explains trade-offs between them.
• Dependency & metric inspection: Detects cyclic dependencies, computes Ca/Ce/Instability (I) and estimates abstraction ratio to locate "Zone of Dor" or "Zone Inútil".
• Actionable recommendations: Produces per-package verdicts, evidence (classes/dependencies involved), and concrete reorganization or refactoring suggestions for architecture reviews and library design decisions.
• Use cases: architecture review, pre-release cleanup, refactor planning, decision between feature-based vs layer-based organization.

Quick Start

Ask the assistant to analyze the repository's packages and return per-package veredict, Ca/Ce/I metrics, evidence of violations, and concrete refactoring recommendations.