What problem does it solve? Hand-written Nodefony services often compile and pass tests yet remain invisible to the dependency injection container, producing silent undefined failures at runtime. This Skill ensures services are created with the generator and properly registered so the container actually knows them. ## Core Features & Use Cases - Service scaffolding: Runs nodefony create service to generate an @injectable() class extending Service, its interface, and its registration in the target's @services([...]) declaration. - Dependency wiring: Uses --inject to declare constructor dependencies via @inject, with pre-write validation that refuses missing targets and self-injection. - Name disambiguation: Clarifies the distinction between the class name used by @inject("BillingService") and the instance name used by container.get("billing"). - Verification workflow: Uses nodefony doctor and nodefony inspect services to prove the container actually holds the service at boot. - Use Case: You need shared business logic (e.g., a Billing service) callable from other services; the Skill generates it, registers it, injects its dependencies, and verifies container registration. ## Quick Start Ask the assistant to create an injectable Nodefony service named Billing and verify it appears in the container with nodefony inspect services.
