Documentation
README
Improve Codebase Architecture
Look for architectural friction that a focused structural change could reduce. Favor improvements that shrink interfaces, concentrate related complexity, and make important behavior easier to test and understand.
Scope the investigation
Follow the user's named subsystem or pain point. Otherwise use recent changes, repeated maintenance friction, test difficulty, or dependency structure to select a useful area. Read relevant domain language and ADRs when present so recommendations respect intentional boundaries.
Use the codebase-design skill when its deep-module vocabulary will sharpen the
analysis. Explore independently in parallel only when the repository is large
enough to benefit and the lanes do not duplicate work.
This is the opening of the README. Read the full README on GitHub.