Best agent skills for codebase architecture
Create deeper module boundaries and durable domain language for agent-maintained systems.
How to choose
Matt offers the more opinionated architecture vocabulary through deep modules, clean seams, and active domain modeling. Pstack settles caller usage and module shape before code crosses a boundary and maps downstream risk, while Addy complements it with stable interface design and durable ADRs.
Codebase Design
Designs deep modules with small interfaces, clean seams, and testable behavior.
Our take: Codebase Design gives agents a compact architectural vocabulary centered on deep modules, narrow interfaces, locality, and testable seams. It improves design conversations without pretending that a generic architecture pattern fits every repository.
Domain Modeling
Sharpens project terminology, edge cases, context documents, and architectural decisions.
Improve Codebase Architecture
Surveys a codebase for high-leverage opportunities to deepen module boundaries.
Architect
Settles caller usage, types, and module shape before code crosses a function boundary.
Blast Radius
Traces what a small-looking change could break and proves the one safety assumption by running code rather than asserting it.
Our take: Blast Radius answers the question agents usually hand-wave: what else could this change break? It traces dependents and callers, then requires the one safety-critical assumption to be proven by running code rather than asserted in prose.
API and Interface Design
Designs stable public APIs, module contracts, and frontend-backend boundaries.
Documentation and ADRs
Captures architectural context and decisions that future engineers and agents need.