Why should you care?

Teams shipping dozens of kernel plugins need consistent snippets and test stubs aligned with AgentNest patterns.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// tools/AgentNest.TemplateGenerator/Program.cs
// dotnet run -- new-plugin Crm.InvoicePlugin
var template = $$"""
public sealed class {{name}}(/* inject deps */)
{
    [KernelFunction, Description("{{description}}")]
    public Task<string> RunAsync(CancellationToken ct) => Task.FromResult("implement");
}
""";
await File.WriteAllTextAsync($"AgentNest.Plugins/{name}.cs", template);

What happened?

• CLI template generator scaffolds KernelFunction plugin class following AgentNest naming and DI conventions.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Run template generator for new plugin or agent class.
2. Fill Description and inject ICrmRepository or similar.
3. Add matching unit test file in AgentNest.Plugins.Tests.
4. Extend generator to emit xUnit Theory rows from OpenAPI path.
5. Integrate generator as dotnet new template pack.

Remember

Internal coding assistant accelerates AgentNest plugin scaffolding. Templates enforce KernelFunction and DI patterns. Always add tests when generating new tools.

Plugin sprint velocity

Team adds five ERP kernel functions in one sprint.

Outcome: Template generator plus Copilot in IDE cuts boilerplate time; consistent audit attributes included.