agentleFS
yuniorsfyuniorsf/GeoAssets/.claude/skills/csharp-conventions/SKILL.md

csharp-conventions

Skill2 starsChanged 18 days agoMITView on GitHub

C# and .NET engineering conventions, design patterns, and language-feature guidance distilled from external books and articles, curated for the GeoAssets codebase (.NET 10). Use when writing or reviewing C# code, choosing between design patterns or type-hierarchy shapes, or evaluating whether a new C#/.NET language feature is safe to adopt.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every entry records status: current (usable today on .NET 10 / C# 14) or future (depends on a language/runtime version GeoAssets doesn't …

    line 23
  2. Distinctive:

    write code that uses it,

    line 32
  3. Distinctive:

    treat its syntax/behavior as final — preview features change shape before GA.

    line 33
  4. Distinctive:

    Do surface it when the user is explicitly asking about roadmap, upcoming language features, or planning a future migration.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

C# Conventions

Distilled, source-attributed engineering guidance — not a restatement of things you already know. Each reference file below traces back to a specific book or article; when a claim from a source turns out to be wrong or superseded, fix it at the source file, don't just override it in a conversation.

How this skill is organized

  • references/ holds one file per topic. Read only the file relevant to the task at hand — don't load the whole set speculatively.
  • Every entry records status: current (usable today on .NET 10 / C# 14) or future (depends on a language/runtime version GeoAssets doesn't target yet).

Before recommending anything from a future entry

GeoAssets targets .NET 10. Any entry marked future describes a preview or unshipped feature. Do not:

  • suggest it as the fix for a current code review or design question,
  • write code that uses it,
  • treat its syntax/behavior as final — preview features change shape before GA.

Do surface it when the user is explicitly asking about roadmap, upcoming language features, or planning a future migration.

References

FileTopicStatus
future-language-features.mdClosed hierarchies, union types, closed enums (C# 15 / .NET 11)future — GA targeted November 2026
code-quality-metrics-and-safe-coding.mdCyclomatic complexity, coupling, IDisposable, static analysis toolingcurrent
code-reusability-and-net-libraries.mdDRY, the reuse lifecycle, .NET Standard vs. netX.0, refactoring triggers, NuGet/OpenAPIcurrent
design-patterns-and-dotnet.mdSOLID, GoF patterns, dependency injection lifetimes, .NET Generic Host, AI-agent patternscurrent
domain-driven-design.mdBounded contexts, entities/value objects/aggregates, Onion architecture, repository/UoW, CQRScurrent
testing-strategy-and-dotnet-tooling.mdUnit/integration/acceptance tiers, TDD/BDD, xUnit/Moq, subcutaneous-test pitfallscurrent
entity-framework-core-and-onion-architecture.mdEF Core configuration/migrations, global query filters, EF-entity-vs-aggregate tensioncurrent
async-and-concurrency-conventions.mdasync/await naming, ConfigureAwait, Task vs ValueTask, cancellation, fire-and-forgetcurrent
nullable-reference-types.md?/!/required usage, nullable-oblivious boundaries, entity/persistence nullabilitycurrent
error-handling-and-result-pattern.mdExceptions vs. Result, translating domain exceptions across a REST boundarycurrent
records-vs-classes.mdGeneral type-shape decision rule: identity/lifecycle vs. value/data-in-motioncurrent
project-and-solution-structure.mdFolder-as-dependency-lane rules, namespace-mirrors-path, one project per backendcurrent
configuration-and-options-pattern.mdOptions classes, SectionName convention, IOptions vs IOptionsSnapshot/Monitorcurrent
api-design-conventions.mdMinimal API grouping, route/verb conventions, request validation, error-shape conventionscurrent
domain-test-data-builders.mdWhen/how to promote ad-hoc geometry/topology test construction into shared builderscurrent
rest-provider-contract-testing.mdClosing the untested seam between the REST server endpoints and REST client repositorycurrent
timeprovider-and-clock-abstraction.mdNever DateTime.Now/Stopwatch/raw timers — inject TimeProvider; ties to active XD01-34 migrationcurrent

As more books/articles are added, list them here with topic and status so this table stays the single index of what's been curated.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.