keyed-service

使用方法

复制安装命令，在自己的智能体环境安装前先检查源码包。
从原始文档核对所需工具、凭据和支持的宿主。
说明输入材料与期望交付物，并对照来源检查输出。

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

开始前需了解

安装不包含模型订阅、API 额度或访问文件的权限。
仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。

仓库原始内容

按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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.