| name | improve-codebase-architecture |
| description | Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. |
| disable-model-invocation | true |
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 vault-backed domain model and uses one architecture vocabulary: module, interface, depth, seam, adapter, leverage, and locality. A module is deep when a small interface hides substantial implementation. The interface is the test surface. One adapter suggests a hypothetical seam; two adapters establish a real one.
Process
1. Explore
Load /vault, then read project context and relevant decision artifacts with vlt context show, vlt search --type decision, and vlt read.
Then use the Agent tool with subagent_type=Explore to walk the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:
- Where does understanding one concept require bouncing between many small modules?
- Where are modules shallow — interface nearly as complex as the implementation?
- Where have pure functions been extracted just for testability, but the real bugs hide in how they're called (no locality)?
- Where do tightly-coupled modules leak across their seams?
- Which parts of the codebase are untested, or hard to test through their current interface?
Apply the deletion test to anything you suspect is shallow: would deleting it concentrate complexity, or just move it? A "yes, concentrates" is the signal you want.
2. Present candidates as an HTML report
Write a self-contained HTML file to the OS temp directory so nothing lands in the repo. Resolve the temp dir from $TMPDIR, falling back to /tmp (or %TEMP% on Windows), and write to <tmpdir>/architecture-review-<timestamp>.html so each run gets a fresh file. Open it for the user — xdg-open <path> on Linux, open <path> on macOS, start <path> on Windows — and tell them the absolute path.
The report uses Tailwind via CDN for layout and styling, and Mermaid via CDN for diagrams where a graph/flow/sequence reliably communicates the structure. Mix Mermaid with hand-crafted CSS/SVG visuals — use Mermaid when relationships are graph-shaped (call graphs, dependencies, sequences), and hand-built divs/SVG when you want something more editorial (mass diagrams, cross-sections, collapse animations). Each candidate gets a before/after visualisation. Be visual.
For each candidate, render a card with:
- Files — which files/modules are involved
- Problem — why the current architecture is causing friction
- Solution — plain English description of what would change
- Benefits — explained in terms of locality and leverage, and how tests would improve
- Before / After diagram — side-by-side, custom-drawn, illustrating the shallowness and the deepening
- Recommendation strength — one of
Strong, Worth exploring, Speculative, rendered as a badge
End the report with a Top recommendation section: which candidate you'd tackle first and why.
Use vault context vocabulary for the domain and the architecture vocabulary above for structure. If the glossary defines "Order," talk about "the Order intake module," not its incidental class name.
Decision conflicts: surface a candidate that contradicts a vault decision only when measured friction justifies reopening it. Mark the conflict and link the decision artifact.
See HTML-REPORT.md for the full HTML scaffold, diagram patterns, and styling guidance.
Do NOT propose interfaces yet. After the file is written, ask the user: "Which of these would you like to explore?"
3. Grilling loop
Once the user picks a candidate, run the /grilling skill to walk the design tree with them — constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
Side effects happen inline as decisions crystallize — run the /domain-modeling skill to keep the domain model current as you go:
- Naming a deepened module after a new domain concept? Use
/domain-modeling and vlt context set when the term resolves.
- Sharpening a fuzzy term? Update vault context immediately.
- Rejecting a candidate for a load-bearing reason? Offer a vault
decision artifact when future reviews need the reason to avoid repeating the proposal.
- Exploring alternative interfaces? Design two materially different interfaces in isolated passes, then compare their leverage, locality, and test seams before choosing.
