dependency-injector

To wire a dependency graph in TypeScript, this Skill generates a single diBootstrap.ts composition root that orchestrates ApiDataSource, RepositoryImpl, and UseCase wiring with constructor injection. It enforces loose coupling by validating graph ordering and constructor signatures before generating the bootstrap file.

Circular dependency breaks clean architecture wiring because instantiation order becomes non-deterministic. This Skill audits the dependency graph to surface tight-coupling and circular dependency issues before code generation, ensuring deterministic instantiation from ApiDataSource through RepositoryImpl to UseCase artifacts.

You generate a composition root for constructor injection by running the orchestrator after upstream skills produce ApiDataSource, RepositoryImpl, and UseCase artifacts. It outputs a diBootstrap.ts file that constructs concrete classes and returns a typed ThunkExtra for Redux store wiring.

Yes, this dependency injection approach integrates with existing Redux store infrastructure by producing an advisory store wiring snippet. This snippet guides ThunkExtra integration with shared app infrastructure without overwriting your existing shared files or store configuration.

The one-entrypoint rule for dependency injection bootstrapping requires all feature wiring to pass through a single diBootstrap.ts file. This Skill enforces the rule by validating that ApiDataSource, RepositoryImpl, and UseCase dependencies are exclusively resolved through this composition root.

Yes, you need to build Data Layer and Domain artifacts before wiring dependencies. The orchestrator runs after upstream Data Layer Builder, Domain Extraction, and Redux State Generator skills to ensure ApiDataSource, RepositoryImpl, and UseCase artifacts exist for deterministic graph construction.