dependency-wirer

Automate wiring components into VitalArc's DependencyContainer with Swift declarations.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tanujsutaria/VitalArc --skill dependency-wirer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-wirer
Source: https://github.com/tanujsutaria/VitalArc/tree/main/.claude/skills/dependency-wirer
Command: npx skills add https://github.com/tanujsutaria/VitalArc --skill dependency-wirer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates wiring new components into VitalArc's DependencyContainer to enable repository, use case, and ViewModel integration.

Core Features & Use Cases

  • Identify injection points in DependencyContainer.swift.
  • Add repository properties and use case initializations.
  • Automate environment setup and optional SwiftData model wiring when needed.
  • Track wiring tasks using Plan-style task creation and updates.

Quick Start

Example workflow: wire a new feature by adding its repository, use cases, and view-model wiring to DependencyContainer.swift, then apply edits and validate the container builds.

Frequently Asked Questions about dependency-wirer

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

FAQPage Schema
How do I wire new components into a Swift dependency injection container?

Automating dependency injection wiring involves updating initialization sequences and adding repository properties and use case initializations to your container. This enforces the DI pattern and ensures repository, use case, and ViewModel integration.

How does SwiftData model wiring work when adding new features to a DI container?

SwiftData model wiring updates initialization sequences and generates necessary Swift declarations to connect data models. It ensures the dependency container properly manages the SwiftData lifecycle during feature integration.

Can I use automated code generation for iOS dependency injection across multiple modules?

Yes, automated code generation supports adding features across multiple iOS modules by tracking wiring tasks and generating Swift declarations. This enforces the dependency injection pattern and ensures correct initialization sequences.

What is the best way to update initialization sequences when adding repositories and use cases?

The best way to update initialization sequences is automating environment setup and applying edits to the container file. This ensures repositories and use cases are correctly initialized and the container builds successfully.

Why does adding new ViewModels break my dependency container initialization?

Adding ViewModels breaks dependency container initialization when injection points are missed or sequences are outdated. Automating the wiring process tracks tasks, updates properties, and validates the container build.