You are about to...	Load
add a `Channel<>`, `lock`, `SemaphoreSlim`, `Interlocked`, `Thread`, or other synchronization / producer-consumer code	`csharp-concurrency-patterns`
define a type where allocation or memory layout matters (struct vs class, `readonly struct`, pooling, `Span`)	`type-design-performance`
(de)serialize JSON, reuse `JsonSerializerOptions`, or add a `JsonSerializerContext`	`serialization`
register services, build an `Add*` extension, or reason about DI lifetimes	`dependency-injection-patterns`
choose or implement a GoF design pattern (factory, strategy, observer, undo/redo, plugin seams) or fix pattern misuse	`personal-csharp-design-patterns`
bind or validate settings - `IOptions`, `IValidateOptions`, startup validation	`microsoft-extensions-configuration`
model a domain type - aggregate, value object, domain event, strongly-typed ID	`ddd`
decide which layer something belongs in, or define a cross-layer port	`clean-architecture` (or `vertical-slice-architecture` for feature-folder projects - load exactly one)
add or upgrade a NuGet package, or edit `Directory.Packages.props`	`package-management`
set up a new project, `.slnx`, `Directory.Build.props`, or `global.json`	`dotnet-project-structure`
inspect a compiled assembly's real API or behavior	`ilspy-decompile`
check a diff for reward-hacking or coverage risk before claiming done	`dotnet-slopwatch` + `crap-analysis`

Notes

Router, not a copy: this lists where to look, not the guidance itself. Load the named skill.
The real trigger is the artifact - the construct, command, or file in the left column - not "am I doing .NET". In a specific repo, that repo's CLAUDE.md binds these to its own file names.
Companion, not optional: load personal-csharp whenever you write or refactor C# - general syntax / naming / structure plus runtime conventions like async / logging / DateTime. This router only covers the specialized areas in the table above; it does not replace personal-csharp.
Cross-cutting non-.NET concerns - security (/security-review), context7 (library docs), git, /code-review - are general flow, not .NET-specific; they live in the project's CLAUDE.md, not in this router.
Routed elsewhere, not here: EF / schema, tests, and ASP.NET Core web live in the project's CLAUDE.md artifact map (-> efcore-patterns + personal-database-conventions, personal-dotnet-testing, personal-dotnet-web-backend); read-path performance (database-performance) lives in personal-database-conventions.

personal-dotnet