Improve Codebase Architecture

Focus on real structural problems that are visible in the codebase. Prefer incremental improvements over rewrites.

Workflow

1. Inspect the relevant parts of the codebase and gather evidence.
2. Identify concrete pain points such as duplication, poor boundaries, oversized modules, cross-layer leakage, weak typing, or dependency tangles.
3. Summarize the current state briefly.
4. Propose a small set of realistic improvements with tradeoffs.
5. If the user wants implementation, apply the smallest change that proves the improvement and protect it with tests.

What to Look For

• duplicated logic that should live in packages/*
• domain logic mixed into UI or transport layers
• modules that have grown too large to reason about
• unnecessary abstractions that can be removed
• unstable dependency direction or circular coupling
• data shapes that leak across unrelated layers

Standards