Improve Codebase Architecture

Use this skill when local cleanup is not enough and the problem is architectural shape: too many shallow modules, leaky seams, or a design that is hard to test through the public interface.

When to Use

• The codebase is correct enough to run, but hard to extend safely
• Understanding one concept requires bouncing across too many tiny modules
• Tests are brittle because the interesting behavior leaks across current seams
• A refactor candidate needs architectural reasoning before code changes start

When NOT to Use