Skill

dotnet-project-init

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

Install

npx claudepluginhub zdanovichnick/dotnet-pilot --plugin dotnet-pilot-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

next-compile

1 file

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

vercel-next-js-2

139.2k

Stats

Stars0

Forks0

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

.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

Indicator	Detection
Test runner	xunit → `xunit` package; NUnit → `NUnit` package; MSTest → `MSTest.TestAdapter`
Mocking	`Moq`, `NSubstitute`, `FakeItEasy` in test project packages
Assertions	`FluentAssertions`, `Shouldly` in test project packages
ORM	`Microsoft.EntityFrameworkCore` → EF Core; `Dapper` → Dapper
Validation	`FluentValidation` or DataAnnotations (check for `[Required]` attributes)
CQRS	`MediatR` package presence
Mapping	`AutoMapper` 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