keyed-service

How to use

Copy the installation command and review the source package before installing it in your own agent environment.
Check the source document for required tools, credentials and supported hosts.
Describe your input and desired deliverable; review the output against the source material.

npx skills add https://github.com/haxen/skills-test --skill keyed-service

Before you start

Installation does not include a model subscription, API allowance or permission to access your files.
Repository stars and installation counts describe activity, not an independent quality or security test.

Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

modul-connect/naming-conventions/keyed-service

C# Keyed Service Naming Convention

Rule Definition

When generating or refactoring C# constructors using the [FromKeyedServices] attribute, the parameter name must be derived from the Key Argument rather than the Interface Type.

Logic & Transformation

Source of Truth: Use the value inside [FromKeyedServices(...)] (e.g., ModulConnect.Queries.Postgres.Backoffice).
Identifier Extraction: Take the last segment of the Key (e.g., Backoffice).
Contextual Suffixing: - If the namespace contains .Queries., append Query.

If the namespace contains .Commands., append Command.

Casing: Convert the result to camelCase for the parameter and _camelCase for the private field.

Examples

✅ Correct (Key-Derived)

csharp

public class OrderProcessor(
    [FromKeyedServices(ModulConnect.Queries.Postgres.Backoffice)] 
    IDataAccess backofficeQuery) 
{
    private readonly IDataAccess _backofficeQuery = backofficeQuery;
}

❌ Incorrect (Type-Derived)

csharp

// DO NOT use the interface name "dataAccess"
public class OrderProcessor(
    [FromKeyedServices(ModulConnect.Queries.Postgres.Backoffice)] 
    IDataAccess dataAccess) 
{ 
    /* ... */ 
}

Rationale

In a modular architecture, the interface (e.g., IDataAccess) defines the contract, but the Key defines the instance's specific responsibility. Naming the parameter after the Key prevents naming collisions when multiple implementations of the same interface are injected and provides immediate semantic clarity.