container-macro

Validate Rust dependency injection graphs at compile time.

Updated May 10, 2026
One-click install
npx skills add https://github.com/jymchng/injectable --skill container-macro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-macro
Source: https://github.com/jymchng/injectable/tree/main/skills/container-macro
Command: npx skills add https://github.com/jymchng/injectable --skill container-macro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides compile-time dependency injection graph validation, helping to detect circular dependencies, scope mismatches, and missing dependencies before runtime.

Core Features & Use Cases

  • Compile-time Validation: Detects circular dependencies, scope mismatches, and missing dependencies.
  • Explicit Registration: Allows explicit registration of dependencies for strict dependency setup validation.
  • Use Case: When building a Rust application that requires compile-time checks for dependencies to ensure a robust and error-free dependency graph.

Quick Start

Use the container-macro skill to define your dependency graph at compile time and catch any potential issues early.

Frequently Asked Questions about container-macro

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

FAQPage Schema
How do I detect circular dependencies in a Rust dependency injection graph at compile time?

You can detect circular dependencies by applying compile-time dependency injection graph validation to your Rust application, which identifies circular dependencies, scope mismatches, and missing dependencies before runtime execution begins.

What is compile-time dependency injection validation in Rust?

Compile-time dependency injection validation is the process of verifying a Rust application's dependency graph during compilation to detect circular dependencies, scope mismatches, and missing dependencies, ensuring strict dependency setup and error-free execution before the program runs.

How do I set up explicit dependency registration for compile-time checks in Rust?

Explicit dependency registration allows strict dependency setup validation by requiring dependencies to be explicitly registered, enabling the compiler to validate the entire dependency graph and detect missing dependencies or scope mismatches during the build process.

Does compile-time dependency injection work for catching scope mismatches and missing dependencies in Rust?

Yes, compile-time dependency injection validation in Rust explicitly catches scope mismatches and missing dependencies alongside circular dependencies, ensuring all dependencies are correctly registered and scoped before the application is allowed to run.

When do I need compile-time dependency graph validation for my Rust application?

You need compile-time dependency graph validation when building a Rust application that requires strict dependency management, ensuring a robust and error-free dependency graph by catching circular dependencies and scope mismatches early in the development workflow.