build-maintainable-software

Refactoring for maintainability requires preserving behavior, reducing risk, and validating invariants with tests at the right level. This skill guides small incremental changes, clear module ownership, explicit boundaries, and predictable control flow to ensure software stays readable.

Designing API boundaries involves improving module ownership, dependency direction, naming, and API surfaces to prevent future misuse. This process ensures readable, simple structures with explicit boundaries and predictable control flow for safely changeable software.

A safe testing strategy validates invariants with tests at the right level, including unit, integration, and e2e tests. This ensures right-sized testing coverage for safe changeability during feature work, refactors, and architecture decisions across any stack.

Yes, this applies to cross-language code reviews in any tech stack. It enforces readability, simplicity, modularity, and testability for feature work, architecture decisions, API boundary design, naming, and refactors using a repository review checklist for final validation.

Broad rewrites driven by style are avoided because they introduce unnecessary risk and bypass focused guidance. Instead, this approach enforces small incremental changes and uses the smallest needed references to validate invariants without broad rewrites.