Modern C# for .NET
Trigger On
- the repo wants more modern idiomatic C# code
- a change depends on language-version compatibility
- the team is upgrading or reviewing C# feature usage across versions
- you need to know whether a C# 13 or C# 14 feature is safe to use
Value
- produce a concrete project delta: code, docs, config, tests, CI, or review artifact
- reduce ambiguity through explicit planning, verification, and final validation skills
- leave reusable project context so future tasks are faster and safer
Do Not Use For
- non-C# .NET languages such as F# or VB
- analyzer-only or formatter-only setup with no language feature choice
Inputs
- target
TFM or TFMs
- explicit
LangVersion, if any
- current SDK version
- team style rules in
.editorconfig and AGENTS.md
Quick Start
- Read the nearest
AGENTS.md and confirm scope and constraints.
- Run this skill's
Workflow through the Ralph Loop until outcomes are acceptable.
- Return the
Required Result Format with concrete artifacts and verification evidence.
Workflow
- Detect the real language ceiling from the repo's target framework and explicit
LangVersion.
- Prefer stable features that the current repo actually supports.
- Use modern syntax when it reduces ceremony, improves correctness, or makes invariants clearer.
- Do not mass-rewrite a codebase into newer syntax unless the repo wants that churn.
- Treat preview features as opt-in only. Never assume preview because the current machine has a newer SDK.
- Pay special attention to C# 13 and C# 14:
- C# 13 is the stable language for
.NET 9
- C# 14 is the stable language for
.NET 10
- When feature selection changes architecture, style rules, or generated-code patterns, coordinate with:
dotnet
analyzer-config
architecture
- After feature-driven refactors, run the repo's .NET quality pass through
dotnet.
Bootstrap When Missing
If the requested C# feature depends on SDK or language support the repo does not have yet:
- Detect current state:
dotnet --list-sdks
rg -n "TargetFramework|LangVersion|TargetFrameworks" -g '*.csproj' -g 'Directory.Build.*' .
- Confirm whether the repo wants to stay on the current stable language level or intentionally upgrade.
- If the feature requires a newer supported SDK or target framework, upgrade the repo toolchain deliberately instead of relying on the local machine by accident.
- If the repo needs explicit
LangVersion, record it in project or shared MSBuild config.
- Run
dotnet build SOLUTION_OR_PROJECT after the feature or toolchain change and return status: configured or status: improved.
- If the repo intentionally stays below the required language level, return
status: not_applicable.
Deliver
- modern C# code that fits the repo's real language version
- fewer obsolete patterns when a newer stable feature is clearer
- no accidental preview or unsupported-language drift
Validate
- the chosen syntax is supported by the repo's
TFM and LangVersion
- the feature improves clarity, correctness, or maintainability
- preview-only features are used only when the repo explicitly opted in
- style and analyzer rules still agree with the new syntax
Ralph Loop
Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.
- Plan first (mandatory):
- analyze current state
- define target outcome, constraints, and risks
- write a detailed execution plan
- list final validation skills to run at the end, with order and reason
- Execute one planned step and produce a concrete delta.
- Review the result and capture findings with actionable next fixes.
- Apply fixes in small batches and rerun the relevant checks or review steps.
- Update the plan after each iteration.
- Repeat until outcomes are acceptable or only explicit exceptions remain.
- If a dependency is missing, bootstrap it or return
status: not_applicable with explicit reason and fallback path.
Required Result Format
status: complete | clean | improved | configured | not_applicable | blocked
plan: concise plan and current iteration step
actions_taken: concrete changes made
validation_skills: final skills run, or skipped with reasons
verification: commands, checks, or review evidence summary
remaining: top unresolved items or none
For setup-only requests with no execution, return status: configured and exact next commands.
Load References
- references/patterns.md
- references/migration.md
- references/csharp-modern-features.md
Example Requests
- "Make this C# code more modern."
- "Which features can we use on .NET 9?"
- "Review this repo for C# 13 or C# 14 opportunities."
1---2name: modern-csharp-33description: "Write modern, version-aware C# for .NET repositories while staying compatible with the repo's target framework and language-version policy. USE FOR: modern idiomatic C# code; language-version compatibility decisions; upgrading or reviewing C# feature usage across versions. DO NOT USE FOR: non-C# .NET languages such as F# or VB; analyzer-only or formatter-only setup with no language feature choice. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."4compatibility: "Requires a C# or .NET repository; respects explicit `LangVersion` and target framework settings."5metadata:6 source: https://skillmd.com/skills/managedcode/modern-csharp-37---89# Modern C# for .NET1011## Trigger On1213- the repo wants more modern idiomatic C# code14- a change depends on language-version compatibility15- the team is upgrading or reviewing C# feature usage across versions16- you need to know whether a C# 13 or C# 14 feature is safe to use1718## Value1920- produce a concrete project delta: code, docs, config, tests, CI, or review artifact21- reduce ambiguity through explicit planning, verification, and final validation skills22- leave reusable project context so future tasks are faster and safer2324## Do Not Use For2526- non-C# .NET languages such as F# or VB27- analyzer-only or formatter-only setup with no language feature choice2829## Inputs3031- target `TFM` or `TFMs`32- explicit `LangVersion`, if any33- current SDK version34- team style rules in `.editorconfig` and `AGENTS.md`3536## Quick Start37381. Read the nearest `AGENTS.md` and confirm scope and constraints.392. Run this skill's `Workflow` through the `Ralph Loop` until outcomes are acceptable.403. Return the `Required Result Format` with concrete artifacts and verification evidence.4142## Workflow43441. Detect the real language ceiling from the repo's target framework and explicit `LangVersion`.452. Prefer stable features that the current repo actually supports.463. Use modern syntax when it reduces ceremony, improves correctness, or makes invariants clearer.474. Do not mass-rewrite a codebase into newer syntax unless the repo wants that churn.485. Treat preview features as opt-in only. Never assume preview because the current machine has a newer SDK.496. Pay special attention to C# 13 and C# 14:50 - C# 13 is the stable language for `.NET 9`51 - C# 14 is the stable language for `.NET 10`527. When feature selection changes architecture, style rules, or generated-code patterns, coordinate with:53 - `dotnet`54 - `analyzer-config`55 - `architecture`568. After feature-driven refactors, run the repo's .NET quality pass through `dotnet`.5758## Bootstrap When Missing5960If the requested C# feature depends on SDK or language support the repo does not have yet:61621. Detect current state:63 - `dotnet --list-sdks`64 - `rg -n "TargetFramework|LangVersion|TargetFrameworks" -g '*.csproj' -g 'Directory.Build.*' .`652. Confirm whether the repo wants to stay on the current stable language level or intentionally upgrade.663. If the feature requires a newer supported SDK or target framework, upgrade the repo toolchain deliberately instead of relying on the local machine by accident.674. If the repo needs explicit `LangVersion`, record it in project or shared MSBuild config.685. Run `dotnet build SOLUTION_OR_PROJECT` after the feature or toolchain change and return `status: configured` or `status: improved`.696. If the repo intentionally stays below the required language level, return `status: not_applicable`.7071## Deliver7273- modern C# code that fits the repo's real language version74- fewer obsolete patterns when a newer stable feature is clearer75- no accidental preview or unsupported-language drift7677## Validate7879- the chosen syntax is supported by the repo's `TFM` and `LangVersion`80- the feature improves clarity, correctness, or maintainability81- preview-only features are used only when the repo explicitly opted in82- style and analyzer rules still agree with the new syntax8384## Ralph Loop8586Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.87881. Plan first (mandatory):89 - analyze current state90 - define target outcome, constraints, and risks91 - write a detailed execution plan92 - list final validation skills to run at the end, with order and reason932. Execute one planned step and produce a concrete delta.943. Review the result and capture findings with actionable next fixes.954. Apply fixes in small batches and rerun the relevant checks or review steps.965. Update the plan after each iteration.976. Repeat until outcomes are acceptable or only explicit exceptions remain.987. If a dependency is missing, bootstrap it or return `status: not_applicable` with explicit reason and fallback path.99100### Required Result Format101102- `status`: `complete` | `clean` | `improved` | `configured` | `not_applicable` | `blocked`103- `plan`: concise plan and current iteration step104- `actions_taken`: concrete changes made105- `validation_skills`: final skills run, or skipped with reasons106- `verification`: commands, checks, or review evidence summary107- `remaining`: top unresolved items or `none`108109For setup-only requests with no execution, return `status: configured` and exact next commands.110111## Load References112113- [references/patterns.md](references/patterns.md)114- [references/migration.md](references/migration.md)115- [references/csharp-modern-features.md](references/csharp-modern-features.md)116117## Example Requests118119- "Make this C# code more modern."120- "Which features can we use on .NET 9?"121- "Review this repo for C# 13 or C# 14 opportunities."