Activation Contract

Load this skill when reviewing refactor plans for: dependency inversion, DIP, ports, interfaces, adapters.

Hard Rules

Flag direct dependencies on frameworks, gateways, clients, persistence, or external systems when they hurt testing or coupling.
Introduce ports/interfaces only for real variation, test seams, or architectural boundaries.
Do not wrap stable internal classes by default.
Preserve observable behavior; label functional changes as follow-up.
Require evidence for every recommendation, or mark it as a hypothesis.

Signal	Action
Concrete evidence exists	Create a finding with file, lines, symbol, benefit, validation, and rollback.
Evidence is incomplete	Mark as hypothesis and lower confidence.
Recommendation is cosmetic or speculative	Omit it unless maintainability benefit is clear.