di-helper

Automate tsyringe DI container registration and validation for missing dependencies.

5|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/moasadi/ddd-bun-api-boilerplate --skill di-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: di-helper
Source: https://github.com/moasadi/ddd-bun-api-boilerplate/tree/main/.claude/skills/di-helper
Command: npx skills add https://github.com/moasadi/ddd-bun-api-boilerplate --skill di-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps manage tsyringe DI container registrations by scanning injectable classes, detecting missing registrations, validating injection patterns, and generating ready-to-use registration boilerplate code.

Core Features & Use Cases

  • Scan Injectable Classes to identify candidates for registration
  • Detect Missing Registrations by comparing found vs registered
  • Validate Injection Patterns to ensure token-based injections
  • Generate Registration Code ready to paste into container setup
  • Check Event Listeners and Route Registrations for completeness

Quick Start

Run the DI helper to generate registration boilerplate for a new context (e.g., "Register UserRepository").

Frequently Asked Questions about di-helper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tsyringe dependency injection container registrations?

Automate DI container registrations by scanning injectable classes, detecting missing registrations, and generating ready-to-paste boilerplate code for repositories, use cases, controllers, event listeners, and routes. The helper validates injection patterns and reports misconfigurations like missing @injectable decorators.

How do I detect missing dependency registrations in tsyringe?

Compare scanned injectable classes against registered dependencies to identify gaps. The helper validates token-based injection patterns across multiple contexts and reports which classes lack proper registration or decorators, preventing runtime injection failures.

Can I validate injection patterns in an existing TypeScript container setup?

Validate injection patterns by checking that token-based injections match registered dependencies. The helper confirms @injectable decorators are present, tokens are correct, and all injectable classes across repositories, use cases, controllers, event listeners, and routes are properly configured.

What's the best way to generate DI registration boilerplate for new contexts?

Run the helper against your codebase to scan injectable classes, identify missing registrations, and output complete registration code tailored to each context. Copy the generated boilerplate directly into your container setup to register repositories, use cases, controllers, and other dependencies.

Why would I use a DI helper instead of manual container configuration?

Manual registration scales poorly and introduces misconfigurations. The helper automates detection of missing registrations, validates injection patterns across all contexts, and generates import statements and tokens, eliminating setup errors and saving configuration time.