Explore

Overview

Before changing legacy code, you must understand it. Guessing creates duplication, breaks hidden coupling, and ships the wrong fix.

Core principle: Produce a codebase-grounded, evidence-based exploration report BEFORE writing any implementation code. Every claim in the report must be backed by a concrete file_path:line_number citation.

Design goals the report must optimize for:

• High cohesion, low coupling — scope changes to a single concern
• Reuse over duplication — find and prefer existing utilities, DTOs, services
• Minimal blast radius — touch only code that traces directly to the request
• Style match — follow existing patterns even if you'd do it differently

The Iron Law