dotnet:init

Initialize .NET projects with .claude/ directory and configuration files.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet:init
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet/skills/init
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in setting up a new .NET project with the necessary configuration files and directories, ensuring a clean and standardized starting point.

Core Features & Use Cases

  • Project Initialization: Sets up the .claude/ directory structure required by the plugin.
  • Optional Configuration: Seeds .editorconfig, analyzers, and Directory.Build.props files for .NET quality settings.
  • Use Case: When starting a new .NET project, this Skill automates the setup process, saving time and reducing the risk of missing configuration steps.

Quick Start

Initialize your .NET project with the /dotnet:init command.

Frequently Asked Questions about dotnet:init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize configuration files when setting up a new .NET project?

To standardize .NET project setup, this Skill initializes your project by creating the `.claude/` directory structure and optionally seeding `.editorconfig`, analyzers, and `Directory.Build.props` files for quality and consistency.

What is the best way to bootstrap a .NET monorepo with quality configurations?

Bootstrapping a .NET monorepo involves setting up standardized configuration files. This Skill targets new project setups in monorepos by automating the creation of `.editorconfig` and analyzer configurations to ensure a clean starting point.

Do I need the .NET SDK to initialize my project configuration?

Yes, you need the .NET SDK to initialize your project configuration. The Skill requires standard .NET project files and a functioning .NET SDK to properly set up the directory structure and seed quality settings.

Can I use this to automatically generate Directory.Build.props for my .NET solution?

Yes, you can automatically generate `Directory.Build.props` for your .NET solution. The Skill provides optional configuration seeding that includes `Directory.Build.props`, `.editorconfig`, and analyzers to enforce quality settings across your project.

What configurations are included in .NET project initialization?

Configurations included in .NET project initialization are `.editorconfig` for code style, analyzers for static analysis, and `Directory.Build.props` for MSbuild properties. These are optionally seeded to ensure quality and consistency.