kagents

.NET application architecture — Modular Monolith, Microservices, Clean Architecture for Blazor, MAUI, ASP.NET Core. Solution structure, architecture pattern decisions, technical design. USE FOR: making architecture decisions, structuring solutions, choosing between architectural patterns. DO NOT USE FOR: writing code (use dotnet-developer) or CI/CD pipeline design (use automation-architect). Read-only — decides, never writes code.

CI/CD pipeline architecture, PowerShell module structure, GitHub Packages, release strategy, workflow run analysis. USE FOR: designing pipelines, structuring automation projects, planning release strategies, analyzing workflow run patterns. DO NOT USE FOR: writing PowerShell code (use powershell-engineer), app architecture (use app-architect), or debugging failed runs (load github-actions-debugging skill). Read-only — defines architecture, never writes code.

Azure resources, .NET Aspire integration, Application Insights, OpenTelemetry, monitoring, logging, alerting — always includes EU-sovereign alternatives with cost comparison. USE FOR: cloud infrastructure design, observability setup, Azure resource provisioning. DO NOT USE FOR: writing .NET application code (use dotnet-developer) or app architecture decisions (use app-architect).

Code review for .NET (C# 14) and PowerShell — architecture conformity, best practices, performance, naming, testability, maintainability. Severity levels: Blocker, Important, Improvement, Note. USE FOR: reviewing code quality, checking architecture conformity, pull request reviews. DO NOT USE FOR: security vulnerability scanning (use security-auditor) or writing/fixing code (use dotnet-developer or powershell-engineer). Read-only — reviews only, never edits code.

EF Core database engineering — DbContext design, entity configuration, migrations, schema design, query optimization, seed data, index design. USE FOR: designing database schemas, creating and reviewing migrations, optimizing queries. DO NOT USE FOR: general .NET development (use dotnet-developer) or security audits (use security-auditor).

.NET Aspire AppHost, Service Defaults, integrations (Postgres, Redis), service discovery, health checks, Polly resilience, telemetry pipeline. USE FOR: configuring Aspire orchestration, adding service references, setting up cloud-native distributed applications. DO NOT USE FOR: Aspire integration tests (use aspire-integration-testing) or Azure Monitor alerts (use azure-monitoring).

.NET Aspire integration testing — DistributedApplicationTestingBuilder, AppHost test fixtures, service mocking, health check validation, TUnit with ClassDataSource. USE FOR: writing and debugging integration tests against Aspire-orchestrated services. DO NOT USE FOR: Aspire app configuration (use aspire-architecture) or unit tests without Aspire (use tunit-patterns).

Azure Monitor, Application Insights, OpenTelemetry — metrics, traces, logs, custom Meter/Counter/Histogram, SLO-based alerts, Aspire Dashboard. USE FOR: configuring monitoring pipelines, creating alert rules, instrumenting .NET services with OpenTelemetry. DO NOT USE FOR: Aspire AppHost configuration (use aspire-architecture) or general Azure resource provisioning (use azure-specialist agent).

Blazor Server, WASM, Hybrid, Static SSR patterns for .NET 10 — render mode decisions, component architecture, code-behind, state management, EventCallback, cascading values, @key, IDisposable. USE FOR: building Blazor components, choosing render modes, implementing state management. DO NOT USE FOR: Blazor inside MAUI (use maui-blazor-hybrid) or Blazor UI E2E tests (use playwright-blazor-testing).

Conventional Commits — type/scope/description format (feat, fix, docs, refactor, perf, test, chore, ci), breaking changes, scopes (.NET, CI/CD, PowerShell), SemVer mapping. USE FOR: writing commit messages, validating commit format, understanding version-bump rules. DO NOT USE FOR: release process or branching (use releaseflow-domain) or changelog file creation (use release-management).

3 hooks across 3 events