michaelalber/improve-codebase-architecture

Improve this codebase's architecture using principles from A Philosophy of Software Design (APOSD) by John Ousterhout.

The APOSD module-shape vocabulary this skill names problems with — shallow module, interface, depth, seam, adapter, leverage, locality — is defined in the codebase-design skill. Load it when you need the precise definitions or the deepening/design-it-twice procedures.

Prerequisites

1. Check for CONTEXT.md or UBIQUITOUS_LANGUAGE.md — load if present. These define the canonical vocabulary for all naming decisions.
2. If neither exists: "Domain model not established. Naming recommendations may not align with ubiquitous language. Run domain-model first for best results."

Scoping Phase

Decide where to look before you look — deepening a module only pays off where change is frequent, so scope before scanning.

1. If the user named a module, subsystem, or pain point, take it and skip step 2.
2. Otherwise walk back the commit history (git log --oneline -- <path>, or repo-wide) and rank paths by change frequency. The hot spots are the candidates; let them pull your attention first. If changes are scattered with no clear hot spot, widen the net.

Analysis Phase

Find the worst offenders first, within the scope set above. Use references/DEEPENING.md as a checklist.

1. Shallow modules — interfaces that expose more complexity than they abstract. Red flag: method count approaches implementation line count.

2. Information leakage — implementation details that escape module boundaries. Red flag: two modules both know about the same data format, error type, or ordering.

3. Temporal coupling — callers that must invoke methods in a specific order. Red flag: comments like "call init() before use()" or "must call A before B".

4. Naming mismatches — code symbols that contradict the ubiquitous language. Red flag: UserManager, DataProcessor, Helper — words that reveal no domain meaning.

Refactoring Protocol

For each identified issue:

1. Name the problem using APOSD vocabulary (shallow module, information leakage, etc.)
2. Quantify impact: how many call sites are affected?
3. Propose a refactoring using references/INTERFACE-DESIGN.md patterns
4. Show before/after: current interface → improved interface
5. Estimate effort: S (hours), M (1–2 days), L (1 week)

Priority order: information leakage → shallow modules → temporal coupling → naming

Language Alignment

For every rename proposed:

• Verify the new name appears in CONTEXT.md or UBIQUITOUS_LANGUAGE.md
• If the term is new: add it to UBIQUITOUS_LANGUAGE.md first, then rename
• See references/LANGUAGE.md for naming anti-patterns to avoid

Output

## Architecture Review: [Module / Package Name]

**Issues found:** [N]

| Issue | Type | Call sites affected | Effort | Priority |
|-------|------|---------------------|--------|----------|
| [name] | Shallow / Info leak / Temporal / Naming | [N] | S/M/L | P1/P2/P3 |

### Proposed Refactorings

#### [Issue name]

**Type:** [APOSD category]
**Before:**
[current interface]

**After:**
[improved interface]

**Rationale:** [APOSD principle cited]