What problem does it solve? Dependency injection becomes a tax when modules are too granular, scopes are wrong, or the framework fights the codebase. This Skill helps you design, organize, and repair DI graphs so they provide clear boundaries, testable fakes, and correct lifecycles instead of god-modules and leaks. ## Core Features & Use Cases - Framework Selection: Choose between Hilt, Koin, or manual wiring based on project shape (pure Android, KMP-heavy, small app). - Module & Scope Design: Lay out one DI module per Gradle module, pick correct @InstallIn components or Koin scopes, and apply qualifiers, assisted injection, and lazy injection patterns. - Graph Diagnosis & KMP Strategy: Detect god modules, wrong scopes, circular dependencies, and Android-only Hilt usage in commonMain, then split into bounded contexts with a KMP-compatible wiring strategy. - Use Case: Your AppModule.kt has grown to 30+ @Provides methods and a ViewModel-scoped object is leaking Activity state. Use this Skill to split the graph by domain, fix the scoping, and add a checkModules() test to validate bindings. ## Quick Start Ask the assistant to review my Hilt module organization and propose a scoped, multi-module DI structure for my Android app.
