decouple

Analyze the code at $ARGUMENTS (or the current working directory if no path given) for tight coupling and suggest how to decouple using dependency injection.

Process

1. Read the code — Find and read ALL Python files in the target path recursively. Read every .py file. Map imports between modules.

2. Identify coupling issues — Look for:

   • Concrete imports — modules importing concrete classes instead of depending on abstractions
   • Global mutable state — module-level variables shared across files
   • Content coupling — accessing private members (_var) of other modules
   • Law of Demeter violations — chained attribute access (a.b.c.method())
   • Circular imports — two modules importing each other
   • God modules — one module imported by nearly everything
   • Missing composition root — object creation scattered across multiple files instead of one place
   • Hard-coded dependencies — import inside functions, direct instantiation instead of injection

3. Generate dependency map — Show which modules depend on which:

   Module Dependencies
   ───────────────────
   routers/booking.py → operations/booking.py, models/booking.py
   operations/booking.py → models/booking.py  (no DB import ✓)
   routers/admin.py → db/models.py             ⚠ concrete DB import
   

4. Propose decoupling — For each issue, show:

   • File and line
   • Principle violated — which of the 7 design principles (P1–P7)
   • Current coupling — what the code does now
   • Decoupled version — using Protocol, Callable, or composition root
   • Before/after code

5. Ask before applying — Use AskUserQuestion to confirm which changes to apply.

6. Apply changes — Edit the files with the approved decoupling.

For guidance on Protocol-based DI, consult ${CLAUDE_PLUGIN_ROOT}/skills/clean-architecture/references/layered-architecture.md and ${CLAUDE_PLUGIN_ROOT}/skills/clean-architecture/references/design-principles.md.