agentsclimarketplace

Dotnet project init

Skill zdanovichnick/dotnet-pilot/skills/dotnet-project-init

Discovers .NET solution context — projects, frameworks, test runners, EF contexts, architecture style, and package management.From its SKILL.md

Install
npx -y skills add zdanovichnick/dotnet-pilot --skill dotnet-project-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

.NET Project Initialization Skill

This skill discovers everything about a .NET solution needed for DotnetPilot to operate effectively.

Discovery Protocol

1. Solution File

  • Search for *.slnx (modern) or *.sln (legacy) in current directory
  • If multiple solutions: ask user which one to use
  • Parse project references from solution file

2. Per-Project Analysis

For each project in the solution:

dotnet list <project.csproj> reference    # project references
dotnet list <project.csproj> package      # NuGet packages

Parse .csproj for:

  • <TargetFramework> → net8.0, net9.0, net10.0, etc.
  • <OutputType> → Exe, Library
  • <Sdk> → Microsoft.NET.Sdk.Web (web), Microsoft.NET.Sdk (classlib)
  • <IsPackable> → library intended for NuGet distribution
  • <RootNamespace> → namespace convention

3. Framework Detection

IndicatorDetection
Test runnerxunit → xunit package; NUnit → NUnit package; MSTest → MSTest.TestAdapter
MockingMoq, NSubstitute, FakeItEasy in test project packages
AssertionsFluentAssertions, Shouldly in test project packages
ORMMicrosoft.EntityFrameworkCore → EF Core; Dapper → Dapper
ValidationFluentValidation or DataAnnotations (check for [Required] attributes)
CQRSMediatR package presence
MappingAutoMapper or Mapster package presence
API style[ApiController] attribute → controllers; MapGet/MapPost → minimal API

4. Architecture Style Detection

Analyze project reference graph:

Clean Architecture:

  • Domain has 0 project references
  • Application references only Domain
  • Infrastructure references Domain + Application
  • Api references Application + Infrastructure

Vertical Slices:

  • Feature folders within a single project
  • No strict layer separation

Flat:

  • Single project or 2 projects (app + tests)

5. EF Core Context Discovery

Search for classes inheriting DbContext:

class *DbContext : DbContext
class *Context : DbContext

For each context, identify:

  • Project location
  • Database provider (from Use* call or package: Npgsql, SqlServer, Sqlite)
  • Migrations assembly location

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.