菜单
Place validation in the correct one of our three scopes in the .NET API — API contract (no DB), Application business via Kommand IValidator, or Domain invariants that throw. Use when adding any validation/guard, or deciding where a check belongs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add a domain entity, aggregate, or value object to the .NET API — rich mutable class with private ctor + static factory (UUIDv7), invariants that throw, tenant_id, 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<T> 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.
| name | validation-scopes |
| description | Place validation in the correct one of our three scopes in the .NET API — API contract (no DB), Application business via Kommand IValidator, or Domain invariants that throw. Use when adding any validation/guard, or deciding where a check belongs. |
| allowed-tools | Read, Glob, Grep, Edit, Write, Bash, Skill, mcp__serena__initial_instructions, mcp__serena__get_symbols_overview, mcp__serena__find_symbol, mcp__serena__find_referencing_symbols, mcp__serena__find_declaration, mcp__serena__find_implementations, mcp__serena__search_for_pattern, mcp__serena__get_diagnostics_for_file, mcp__serena__list_dir, mcp__serena__find_file, mcp__serena__create_text_file, mcp__serena__replace_symbol_body, mcp__serena__insert_after_symbol, mcp__serena__insert_before_symbol, mcp__serena__replace_content, mcp__serena__rename_symbol, mcp__serena__safe_delete_symbol |
Serena MCP is mandatory for C# code. First call
mcp__serena__initial_instructionsto load the Serena tool manual, then use the Serena tools for ALL.csreading / searching / navigation / creation / editing — prefer symbol navigation (get_symbols_overview/find_symbol/find_referencing_symbols) over whole-file reads. NativeEdit/Writeon.csis hook-blocked (the TS/React frontend uses the native tools).
Validation is three distinct concerns; put each check in the right one. Source of truth (the facts —
read them): .claude/rules/backend/api-design.md (§4.1), cqrs-kommand.md, domain-model.md, and
docs/projectStandards/backend-architecture.md §4.1. We do NOT use FluentValidation or any validation
library. C# (.cs) edits via Serena.
| Scope | Where | Validates | On failure |
|---|---|---|---|
| Contract | API endpoint, before dispatch | request shape, required fields, types, and access control inferable from the JWT/cookie | reject → ProblemDetails; never reaches a handler. No DB calls. |
| Business | Application — a Kommand IValidator<T> on the command/query | rules needing data/understanding ("is this buyer ≥18 for alcohol?") | a failed Result (Error.Validation(failures)) → ValidationProblemDetails |
| Invariant | Domain entity factories/methods | an object can never be created or mutated into an invalid state | throw; the handler catches and folds into Result.Failure |
IValidator<T> beside the
command/query (co-located in Commands//Queries/, named …Validator). Surface failures as a failed
Result — prefer a validation interceptor that returns the failed Result<T> over Kommand's throwing
default (see cqrs-kommand reference/patterns.md).add-domain-entity skill). Never rely on outer layers to
keep the domain valid — it's the last line of defence.IValidator already guarantees) — each rule lives in exactly one scope.Result/ProblemDetails (see the result-pattern skill), not ad-hoc exceptions at the boundary.