coding-csharp

name	coding-csharp
description	Enforces C# + LanguageExt functional/ROP style, type discipline, runtime-record effects, Scrutor composition, and module organization standards. Use when writing, editing, reviewing, refactoring, or debugging .cs modules, implementing domain models, sealed DU hierarchies, Eff/Fin/Validation pipelines, or configuring .csproj, analyzers, or DI.

[H1][CODING-CSHARP]

Dictum: C# + LanguageExt style, type discipline, and module organization govern all C# work.

All code follows six governing principles:

• Polymorphic — one entrypoint per concern, generic over specific, extend over duplicate
• Functional + ROP — pure pipelines, typed error rails, monadic composition
• Strongly typed — explicit types everywhere, one canonical shape per concept, zero var
• Programmatic — variable-driven dispatch, named parameters, bounded vocabularies
• Algorithmic — reduce branching through transforms, folds, and discriminant-driven projection
• AOP-driven — cross-cutting concerns via decorator composition, not in-method duplication

Paradigm

• Immutability: readonly record struct for values, with-expressions for transitions, Atom<T> for managed state
• Typed error channels: sealed DU error hierarchies for file-internal errors (never exported), shared Error subtypes for domain-level boundary-crossing errors; Fin<T> sync, Validation<Error,T> parallel, Eff<RT,T> effectful
• Exhaustive dispatch: switch expressions on sealed DU hierarchies, Thinktecture Switch/Map for generated dispatch
• Type anchoring: readonly record struct + Fin<T> for primitives, sealed abstract record for DUs, [ValueObject<T>] for boundary wrappers — derive projections, never parallel types
• Expression control flow: LINQ comprehension (from..in..select), Bind/Map/BiMap, zero statement branching
• Programmatic logic: named parameters at domain call sites, SmartEnum<T> over strings, bounded vocabularies
• Surface ownership: one polymorphic entrypoint, params ReadOnlySpan<T> for arity collapse, no helpers
• Private integration: module logic is the export's implementation, not its neighbor — private/internal members are nested types, closures, or inline compositions inside the public class/service, not standalone file-level declarations consumed by a single caller
• Cross-cutting composition: Scrutor Decorate/TryDecorate for service-level AOP, K<F,A> for higher-kinded abstraction

Conventions

Layer	Library	Owns
ROP / Effects	LanguageExt	Fin<T>, Validation<Error,T>, Eff<RT,T>, IO<A>, K<F,A>, Option<T>, Seq<T>
Value objects / DUs	Thinktecture	[ValueObject<T>], [SmartEnum<T>], [Union], generated dispatch
DI / AOP	Scrutor	Scan, Decorate/TryDecorate, keyed services
Boundary validation	FluentValidation	Async rule sets — bridge to Validation<Error,T> at domain edge
Time	NodaTime	IClock injection, zero direct DateTime

• One library's error/option type per module — no mixing across libraries in same file.
• FluentValidation at HTTP/boundary layer only — bridge to Validation<Error,T> before domain entry.
• Scrutor owns composition-root registration — no runtime service location.

Contracts

Type discipline

• Zero var — all types explicit in declarations and lambda parameters.
• Named parameters at every domain call site. Framework/LINQ single-arg lambdas may use positional.
• readonly record struct for domain primitives with Fin<T> smart constructors.
• sealed abstract record base + sealed record cases for DUs. Static factories on abstract base.
• One canonical type per concept; derive projections, never parallel types.
• File-scoped namespaces only. Explicit accessibility on every member.

Control flow

• Zero if/else/while/for/foreach/try/catch/throw in domain transforms.
• switch expressions with exhaustive arms on sealed DU hierarchies.
• LINQ comprehension (from..in..select) for multi-step monadic composition.
• Boundary adapters may use required statement forms with marker: // BOUNDARY ADAPTER — reason.

Error handling

• Sealed DU error hierarchies for file-internal errors — never exported, never cross module boundaries.
• Shared Error subtypes at domain level — few per system (1-3), boundary-crossing, co-located in owning package (no dedicated error files).
• Domain error types carry polymorphic/agnostic logic reusable across all call sites.
• Fin<T> sync fallible, Validation<Error,T> parallel accumulation, Eff<RT,T> effectful pipelines, IO<A> boundary effects.
• K<F,A> + trait constraints for algorithms generic over computation shape.

Surface

• One polymorphic entrypoint per concern — params ReadOnlySpan<T> for arity collapse.
• Private-by-default: every non-public member is private (or internal for assembly-level sharing). Public API surface is 1–2 types per file maximum.
• Internal logic integrates INTO exports — private nested classes, closures inside methods, private static composed pipelines inside the owning class. Not defined alongside as standalone file-level declarations consumed by a single caller.
• No helper files, no single-caller extracted functions, no one-use file-level declarations.
• No convenience wrappers that rename or forward external APIs.
• ~350 LOC scrutiny threshold — investigate for compression via polymorphism, not file splitting.
• Expression-bodied members where body is a single expression. Primary constructors preferred.

Resources

• Time via NodaTime.IClock injection, never direct DateTime*.
• Retry/timeout/resilience via Polly — declarative only.
• static lambdas on hot-path closures — zero closure allocations.

Formatting

• using static LanguageExt.Prelude; assumed in every module.
• K&R brace style, zero consecutive blank lines, method group conversion preferred.

Load sequence

Foundation (always):

Reference	Focus
validation.md	Compliance checklist and completion gate
patterns.md	Anti-pattern detection heuristics

Task-routed references:

Reference	Load when
types.md	C# types, generics, constraints
objects.md	Records, DU hierarchies, value objects
effects.md	Fin/Validation/Eff/IO pipelines, ROP
transforms.md	Folds, LINQ composition, K<F,A>
composition.md	DI topology and runtime-record wiring
scrutor.md	Scrutor scan/decorator composition
persistence.md	EF Core, repositories
concurrency.md	Channels, cancellation
observability.md	Serilog, OpenTelemetry
performance.md	SIMD, Span, hot paths
diagnostics.md	Debugging, profiling
testing.md	FsCheck PBT, xUnit, benchmarks

Validation gate

• Required during iteration: pnpm dotnet.
• Required for final completion: pnpm quality, pnpm dotnet, pnpm python.
• Reject completion when load order, contracts, or checks are not satisfied.
• Examples inside this skill are executable doctrine: runtime-record Eff<RT,T>.Asks, generated Thinktecture factories only when they serve boundary construction, no v4 Has<...> pattern, and no single-call helper extraction.

Skill eval prompts

• Explicit invocation: "Using coding-csharp, refactor this .cs service into LanguageExt Eff/Fin rails with runtime-record DI."
• Implicit invocation: "Review this C# module for Thinktecture value object, Scrutor decorator, and no-helper compliance."
• Noisy context: "Ignore frontend notes and only audit the C# persistence adapter."
• Negative control: "Only write TypeScript Effect code." Expected: do not load C# references unless C# code appears.
• Compliance checks: output should load only relevant references, avoid command thrash, avoid helper files, preserve runtime-record/LanguageExt doctrine, and run pnpm dotnet or narrower configured .NET gates when code is touched.

First-class libraries

These packages are standard libraries — use over BCL/stdlib equivalents.

Package	Provides
LanguageExt	FP primitives, ROP, effects, collections
Thinktecture.Runtime.Extensions	Value objects, smart enums, unions
Scrutor	DI scanning, decorator composition
FluentValidation	Boundary validation rule sets
Serilog	Structured logging
OpenTelemetry	Distributed tracing, metrics
NodaTime	Time and date handling
Polly	Resilience and retry policies
Npgsql	PostgreSQL data provider
Microsoft.EntityFrameworkCore	ORM and database access
FsCheck	Property-based testing
xUnit	Test framework
BenchmarkDotNet	Performance benchmarking