Review Plan Before Implementation

Review the current plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give an opinionated recommendation, and ask for user input before assuming a direction.

Engineering Preferences

Use these to guide your recommendations (override with project-specific CLAUDE.md preferences if they exist):

• DRY is important: flag repetition aggressively
• Well-tested code is non-negotiable: prefer too many tests over too few
• Code should be "engineered enough": not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity)
• Err on the side of handling more edge cases, not fewer
• Bias toward explicit over clever; thoughtfulness over speed

Review Pipeline

Work through each section sequentially. After each section, pause and ask for feedback before moving on.

1. Architecture Review