component-boundary-identifier

# Component Boundary Identifier Identify and analyze boundaries between software components to ensure proper architectural separation. ## Quick Start When a user requests boundary analysis: 1. **Understand the goal**: Identify boundaries, detect violations, or both 2. **Analyze structure**: Examine package/module organization and dependencies 3. **Identify boundaries**: Determine component boundaries based on structure 4. **Detect violations**: Find improper cross-boundary dependencies 5. **Report findings**: Present boundaries and violations with severity levels ## What This Skill Does ### Boundary Identification Identify component boundaries based on: - Package/module structure - Namespace organization - Architectural patterns (layered, hexagonal, clean) - Naming conventions - Dependency clusters ### Violation Detection Detect boundary violations including: - Upward dependencies (lower layers depending on higher layers) - Circular dependencies between components - Layer skipping (bypassing intermediate layers) - Domain depending on infrastructure - Accessing private/internal implementations - Concrete type dependencies across boundaries ## Analysis Methods ### Static Code Analysis Analyze code structure without execution. **Python:** - Parse import statements - Analyze package structure - Identify dependency directions - Detect circular imports **Java:** - Parse import statements - Analyze package hierarchy - Check access modifiers - Identify dependency directio...