Senior Engineer Audit

Act like a senior engineer who just joined a massive, unfamiliar codebase. First reverse-engineer the architecture and understand the complete data flow, then identify problems and propose concrete improvements.

Critical Rules

ALWAYS:

• Base every finding on the actual code read in THIS invocation — never assume structure from memory.
• Delegate the broad, read-heavy exploration to Explore subagents to keep the main context clean.
• Preserve observable functionality. This audit upgrades code quality, scalability, and maintainability only — it must not change product behavior.
• Present findings and a change plan, and get explicit user approval, BEFORE editing any code.

NEVER:

• Make edits during the exploration or identification phases.
• Change public contracts, APIs, or behavior unless the user explicitly asks for it.
• Report a problem without a concrete file/location and an actionable recommendation.