← ClaudeAtlas

improve-codebase-architecturelisted

Scan a codebase for deepening opportunities, present them as a factory report, then discuss whichever one you pick.
volekerb/hivemill · ★ 33 · AI & Automation · score 78
Install: claude install-skill volekerb/hivemill
<!-- Source: mattpocock/skills skills/engineering/improve-codebase-architecture @ 5beb35b040e3de97e54fa9e386d7e42d15c295c2, MIT (see ../../LICENSE-mattpocock). Modified: HTML report and CDN steps removed, output goes to factory report; grilling skill call and GLOSSARY.md/ADR file writes replaced by factory msg discussion and text proposals in the report. --> # Improve Codebase Architecture Surface architectural friction and propose **deepening opportunities**: refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability. This command is _informed_ by the project's domain model and built on a shared design vocabulary: - Call the Skill tool with "codebase-design" for the architecture vocabulary (**module**, **interface**, **depth**, **seam**, **adapter**, **leverage**, **locality**) and its principles (the deletion test, "the interface is the test surface", "one adapter = hypothetical seam, two = real"). Use these terms exactly in every suggestion, and don't drift into "component," "service," "API," or "boundary." - The domain language in `GLOSSARY.md` gives names to good seams; ADRs in `docs/adr/` record decisions this command should not re-litigate. ## Process ### 1. Explore **Scope before you scan: YAGNI.** Deepening a module pays off by making future changes to it easier, so put extra weight on the parts of the codebase that have recently changed. Decide *where* to look before you look: - If the user named a direction (a module, a s