andes-software-solutions/andes-dotnet
C#/.NET standards as on-demand skills (C# 14, ASP.NET Core Minimal APIs, FluentValidation, Azure Functions, MCP servers, EF Core, xUnit v3 + NSubstitute) and a report-only C# reviewer.
Use when building or reviewing ASP.NET Core Web APIs (Minimal APIs only, never controllers): endpoint groups, TypedResults, FluentValidation endpoint filters, Problem Details, Entra ID/JWT auth, versioning, OpenAPI, caching, rate limits and timeouts, health checks, and container deployment.
Use when building or reviewing Azure Functions in C# (.NET isolated worker): triggers and bindings, host.json and local.settings.json, DI, retries, OpenTelemetry, Flex Consumption hosting, security, testing, and migrating off the retired in-process model.
Use when writing or reviewing asynchronous C# code: async/await, Task vs ValueTask, CancellationToken flow, ConfigureAwait, timeouts, bounded concurrency, IAsyncEnumerable, exception handling, background work, and avoiding sync-over-async deadlocks.
Use when adding or reviewing XML documentation comments on C# public APIs: summary, param, returns, exception, inheritdoc, remarks, and example conventions.
Use when building or reviewing a Model Context Protocol (MCP) server in C# with the ModelContextProtocol SDK: tools, prompts, resources, stdio and HTTP transports, stderr logging, auth, error handling, security, and testing with McpClient.
Use when writing, editing, or reviewing any C# (.cs) code: C# 14 idioms, naming, the mandatory file layout (interface members, then Private methods / Public static methods / Logging regions), primary constructors, collection expressions, var, sealed, TimeProvider, LoggerMessage logging, nullability, credentials and security, and Minimal APIs + FluentValidation.
Use when writing or reviewing .NET tests: xUnit v3 (latest, Microsoft Testing Platform) + NSubstitute only (no FluentAssertions, Moq, NUnit, or MSTest), naming, theories, fixtures, fake time and logging, WebApplicationFactory integration tests, and the Testcontainers → SQLite → test DB → EF InMemory database ladder.
Use when adding, moving, renaming, or registering files, folders, or projects in a .NET Api → Service → Repository → Entity → Common (+ Dto) solution, or asking where a type goes or what to call it: placement, one type per file, type and DI names, options and validators, services querying the DbContext (no repositories), and the test layout.
Use when writing or reviewing Entity Framework Core code: DbContext and entity design, queries, change tracking, migrations, performance, security, and database testing (Testcontainers first, EF InMemory last).
Use when adding or reviewing entities with a Guid or int key, deactivation, audit timestamps, or optimistic concurrency: the BaseEntity<TKey> / BaseCreatedEntity<TKey> / BaseModifiedEntity<TKey> classes and their configurations, the named Deactivation filter, the TimeProvider interceptors, and row-version conflicts as ConflictException.
Use when a column must reference a fixed set of values (status, type, category) as a lookup table tied to a C# enum: BaseEnumEntity<TEnum> with the enum as the key on both sides (stored as int), the sealed row type, BaseEnumEntityConfiguration seeding every member with HasData, enum-typed foreign keys, and the add / rename / never-delete rules for members.
Use when creating, updating, refactoring, explaining, or reviewing Microsoft Agent Framework (.NET) solutions: agents, sessions, tools, workflows, hosting, and migration from Semantic Kernel or AutoGen. Ground APIs in live Microsoft Learn docs.