The definitive read-only authority on the .NET backend — architecture, project structure, every standard/rule, and all canonical patterns. Reviews backend changes (apps/api) for rule adherence and hunts for real bugs, returning severity-bucketed findings. Never edits code.
Read-only frontend reviewer for the Next.js/React app. Validates adherence to the project's own frontend standards and hunts for bugs. Use to review frontend changes under apps/web. Never edits code. (Fully exercised once apps/web is scaffolded.).
Read-only reviewer of the API↔BFF seam and cross-stack concerns — request/response contract parity, ProblemDetails handling, SSE relay, auth/tenancy across the boundary. Use when a change spans apps/api and apps/web. Never edits code.
Adversarially verifies a single architect finding by reading the actual code line by line, returning a real/noise verdict with evidence. Used by the architect-review workflow to pre-filter findings before the main agent's final triage.
Implements an approved implementation plan in the .NET/Next.js codebase. Spawned by the impl-build workflow to build a plan section — edits C# via Serena, builds, and reports files changed. Not for ad-hoc use.
Read-only root-cause investigator for the .NET backend — diagnoses runtime/production issues (errors, anomalies, failures, performance) by combining code analysis, SQL, and telemetry. Produces an evidence-backed root cause + a minimal-fix proposal (a fix-list impl-build can consume). Never edits code.
The backend security authority for the .NET API — audits against OWASP Top 10 (mapped to .NET 10 / Minimal API / EF Core on Npgsql), tenant isolation, secret handling, and EU data residency. Read-only; returns severity-bucketed, verifiable findings. Backend-specific (the frontend has its own auditor).
Writes and runs the tests specified by an implementation plan's exact test list, then reports exact pass/fail/skip counts. Used by the impl-build workflow. Owns test authorship; never weakens a test to make it pass. (Fully exercised once apps/api/tests + an approved test stack exist.).
Read-only validator that checks an implementation against its plan and the project rules and returns a structured pass/fail verdict. Used by the impl-build workflow after the implementer; gates the fix loop. Never edits code.
Runs before the agent uses a tool for Edit, Write, MultiEdit, Bash and PowerShell tool calls, running pwsh (2 commands). From atherio-danp/cde-dotnetcc.
Add a domain entity, aggregate, or value object to the .NET API — rich mutable class with private ctor + static factory (UUIDv7), invariants that throw, tenantid, identity equality; records for value objects. Use when modeling new domain state under apps/api/{{ProjectName}}.Domain.
Add a Minimal API endpoint (a feature/use case) to the .NET API — feature folder, IEndpoint self-registration, contract validation, Kommand dispatch, Result→ProblemDetails. Use when adding or changing an HTTP endpoint under apps/api/{{ProjectName}}.Api.
Author a CQRS command or query in the {{ProductName}} backend using the Kommand library, the three-scope validation model, and the Result failure pattern. Use whenever creating or modifying a command/query/handler/validator in apps/api/{{ProjectName}}.Application, or wiring its endpoint in {{ProjectName}}.Api.
Choose and wire AI features in the .NET backend — LLM calls, agentic tool-calling/multi-step workflows, RAG/vector search, structured output, streaming. Use when adding or changing anything that talks to a model or orchestrates agents (your agentic pipeline). Tailored to our LLM provider + MAF + pgvector stack.
Scan .NET/C# code for performance anti-patterns (async, memory/strings, collections/LINQ, regex, serialization, I/O) with tiered severity, reporting findings without editing. Use when auditing hot paths, reviewing allocation-heavy code, or analyzing the API for optimization opportunities.
Add or change EF Core (Npgsql/PostgreSQL) persistence in the .NET backend — entities, EF configurations, repositories, queries, migrations. Use when adding a table/entity, a query, a repository, or a migration under apps/api.
Optimize EF Core (Npgsql/PostgreSQL) queries in the .NET API — fix N+1, choose tracking modes, use compiled queries, split queries, and avoid translation traps. Use when a query is slow, emits excessive SQL, or causes high DB load. Complements the efcore-patterns scaffolding skill.
Explain how a specific area / file / feature / topic actually works — grounded line-by-line in the real code, with file:line citations. Use when asked to explain, trace, or understand a part of the code (e.g. "explain the model router", "how does the agentic pipeline work", "trace what CreateProject does"). Read-only…
Create, debug, test, and publish MCP (Model Context Protocol) servers in C# using the official ModelContextProtocol SDK — tools/prompts/resources, stdio vs HTTP transport, MapMcp hosting. Use when building or changing an MCP server in the .NET backend (relevant to your agentic pipeline).
Create, run, configure, and interpret BenchmarkDotNet microbenchmarks in the .NET API — measure and compare approaches, runtime configs, or package versions. Use when proving a performance change, comparing implementations, or validating a hot-path optimization. (Not for profiling or load testing.).
Produce a structured "get up to speed on this whole project" orientation — vision, architecture, where things live, conventions, how to do common tasks, current state — grounded in the real code/config with pointers. Optionally writes/updates docs/ONBOARDING.md. Use when asked to onboard, give a project overview, or…
Add or change OpenTelemetry tracing, metrics, and structured logging in the .NET API (apps/api) — OTLP exporter setup, custom ActivitySource spans, IMeterFactory metrics, log/trace correlation. Use when adding observability, custom spans/metrics, or troubleshooting distributed traces.