agentleFS
lod-softworkslod-softworks/mcp-email-management/.agents/skills/dotnet/SKILL.md

dotnet

Skill0 starsChanged 2 months agoMITView on GitHub

C# and .NET coding conventions, project layout, Entity Framework patterns, and Lod Softworks defaults. Use when creating or editing C#/.NET code, solution or project files, naming, or review feedback about .NET code quality.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read guidelines.md for full conventions before making C#/.NET changes.

    line 11
  2. Very specific:

    Use latest stable LTS .NET with <LangVersion>latest</LangVersion>.

    line 16
  3. Very specific:

    Prefer primary constructors, file-scoped namespaces, explicit types over var, new() over new Type().

    line 17
  4. Very specific:

    Do not use the Async suffix on async methods.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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# / .NET

Read guidelines.md for full conventions before making C#/.NET changes.

Quick Reference

  • Dotnet solution files (.slnx / .sln) live at the repository root; source projects live under src/ and test projects live under test/.
  • Use latest stable LTS .NET with <LangVersion>latest</LangVersion>.
  • Prefer primary constructors, file-scoped namespaces, explicit types over var, new() over new Type().
  • Data models and POCOs: record class.
  • Entity Framework Core with annotations (not fluent OnModelCreating); singular table/column names.
  • Namespaces prefixed with Lod.; set Product, Copyright, Company, and Description in .csproj.
  • Do not use the Async suffix on async methods.

For universal code quality rules (naming, SRP, review style), also read .agents/rules/code-guidelines.md.

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.