Improve codebase architecture

Overview

Diagnose structural problems in a codebase or subsystem, then turn the evidence into a practical improvement plan. The plan should simplify the code, support local reasoning, and make verification and handoff easier to bound.

When to Use

• Architecture drift in a repository or subsystem
• Monorepo review across frontend, backend, shared-package, or CI seams
• Plans to simplify code, clean up boundaries, or improve test shape
• Checks against the current skill system and agent-friendly practices
• Decisions about what to preserve or refactor before broader modernization
• Maps of domain language, ownership boundaries, and decisions in an existing complex codebase

When Not to Use