dotnet
Skill54 starsChanged 2 months agoApache-2.0View on GitHub
Use for .NET application development involving services, managers, dependency injection, Microsoft.Extensions.Hosting, dependency direction, MiniDb persistence, DTOs, Mapster mapping, shared entities/helpers, MCP tools, module workflows, solution analysis, cancellation, logging, and logic shared by CLI and Blazor.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- TimyVillarmia/skillstheir own version, first seen Nov 8, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- ChristopherAlphonse/calphonse-skillstheir own version, first seen Nov 1, 2026
- rogue-dev-studio/ai-agents-roguetheir own version, first seen Nov 1, 2026
- lod-softworks/mcp-email-managementtheir own version, first seen Oct 25, 2026
- Mindrally/skillstheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Mindrally/skills★ 275same name
- Postpartum-genushyacinthus29/dotnet-skills★ 13same name
- rogue-dev-studio/ai-agents-rogue★ 2same name
- Sorcha-Platform/Sorcha★ 2same name
- ChristopherAlphonse/calphonse-skills★ 1same name
- conjure-3301/skills★ 0same name
- its-ash/skills★ 0same name
- lod-softworks/mcp-email-management★ 0same name
- muxammadmamajonov/dot-claude★ 0same name
- TimyVillarmia/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
5
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
- Distinctive: line 11
Read the calling surface from CLI or Blazor before changing shared behavior.
- Very specific: line 12
Check shared entities and DefaultDbContext before changing persistence.
- Distinctive: line 17
Put cross-step workflows and external I/O in services.
- Distinctive: line 18
Put MiniDb query/update behavior in managers.
- Distinctive: line 19
Keep app-facing service methods stable when both CLI and Blazor consume them.
- Very specific: line 20
Use existing DTO patterns and Mapster helpers (MapTo, Merge, Adapt) where nearby code does.
- Distinctive: line 24
Keep MCP tools as protocol surfaces: stable parameter names, returned shapes, and no console output.
- Very specific: line 28
Add tests under tests/StudioMod.Tests/Services, Managers, or Commands depending on the observable behavior.
“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.
Files
.NET Application Development
Workflow
- Identify whether the change belongs in an app surface, service, manager, MCP tool, DTO/model, CodeGenerator, or Share.
- Read the calling surface from CLI or Blazor before changing shared behavior.
- Check shared entities and
DefaultDbContextbefore changing persistence. - Preserve dependency direction: app projects depend on CoreMod; CoreMod depends on CodeGenerator and Share; Share stays foundational.
Conventions
- Put cross-step workflows and external I/O in services.
- Put MiniDb query/update behavior in managers.
- Keep app-facing service methods stable when both CLI and Blazor consume them.
- Use existing DTO patterns and Mapster helpers (
MapTo,Merge,Adapt) where nearby code does. - Pass
CancellationTokenthrough file, HTTP, and long-running async operations. - Make HTTP services testable with injectable clients or handlers.
- Log exceptions with structured logging before wrapping them in localized, user-friendly errors.
- Keep MCP tools as protocol surfaces: stable parameter names, returned shapes, and no console output.
Tests
- Add tests under
tests/StudioMod.Tests/Services,Managers, orCommandsdepending on the observable behavior. - Stub HTTP and isolate filesystem/MiniDb state.
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
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.