Standardize Inversify DI bindings with a shared TYPES symbol registry.
npx skills add https://github.com/recca0120/code-quest --skill inversify-di
Please help me install this Agent Skill. Skill: inversify-di Source: https://github.com/recca0120/code-quest/tree/main/.claude/skills/inversify-di Command: npx skills add https://github.com/recca0120/code-quest --skill inversify-di
Inversify dependency injection can become inconsistent and hard to test when service identifiers, bindings, scopes, and overrides are scattered across the codebase.
Use this guidance when updating apps/server/src/container.ts and apps/server/src/types.ts, especially if you are adding a new injectable service, changing binding scopes, or adjusting test-time dependency overrides.
High-intent search queries and answers about installing and using this skill.
A central TYPES symbol registry defines consistent Symbol-based service identifiers for server dependencies. This prevents scattered bindings by providing a single map for all injectable services, ensuring type-safe and uniform resolution across the application.
The best way to override Inversify bindings in a test container is using container.rebindSync-style calls. This approach swaps production bindings with test mocks, though you should note Inversify v8 introduces breaking API changes to this test container setup.
Configuring inline container bindings with singleton scopes involves binding core services directly in the container without using ContainerModule. This ensures services maintain a single shared instance throughout the server application's lifecycle.
Inversify supports constructor injection with optional dependencies using @injectable() and @inject() decorators. This pattern allows practical service wiring, including optional settings injection, preventing brittle bindings when certain dependencies are not strictly required.
Migrating to Inversify v8 introduces breaking API changes specifically relevant to the project's test container setup. The migration guidance calls out these modifications to ensure existing test-time dependency overrides and rebindSync calls function correctly.
Inconsistent service identifiers occur when Inversify dependency injection bindings, scopes, and overrides are scattered across the codebase. Standardizing patterns with a shared TYPES symbol registry prevents this brittleness and ensures uniform service resolution.
ExpertVagabondImplement TypeScript core modules with Domain-Driven Design and dependency injection.
creator-hianConfigure VContainer dependency injection for Unity projects.
ngxtmAutomate Flutter dependency injection setup using injectable and get_it.
twofoldtech-dakotaImplement dependency injection and layered architecture in C#/.NET backend projects.
