Activation Contract

Load this skill when reviewing refactor plans for: type contracts, Object, Map<String,Object>, primitive obsession.

Hard Rules

Flag Object, raw types, Map<String,Object>, stringly typed values, magic strings, casts, and primitive obsession.
Prefer value objects, enums, records, or typed DTOs when they clarify contracts.
Keep public API changes as follow-up unless approved.
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.