init

Initialize .NET projects with .claude/ directory and quality configurations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need to initialize a .NET project with the appropriate directory structure and .NET quality configurations.

Core Features & Use Cases

  • Project Initialization: Creates the .claude/ directory and necessary subdirectories for the plugin to operate.
  • Quality Configuration: Optionally seeds the .editorconfig and Directory.Build.props for .NET-focused settings.
  • Use Case: When you first use the plugin in a new repository or after cloning a repository that already uses the plugin but lacks the .claude/ directory.

Quick Start

Run /dotnet:init to set up your .NET project for the plugin.

Frequently Asked Questions about init

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

FAQPage Schema
How do I initialize a .NET project with quality configuration files?

To initialize a .NET project with quality configuration, run `/dotnet:init` to generate the `.claude/` directory structure and optionally seed `.editorconfig` and `Directory.Build.props` files for maintainability.

What does Directory.Build.props do for .NET project setup?

Directory.Build.props defines MSBuild properties applied across a .NET project, and this initialization process optionally seeds it alongside `.editorconfig` to establish consistent quality configurations from the start.

When do I need to set up the .claude directory structure in my repository?

You need to set up the `.claude/` directory structure when first using the plugin in a new repository or after cloning a repository that uses the plugin but lacks the required directory for operation.

Can I seed .editorconfig during .NET project initialization?

Yes, you can seed `.editorconfig` during .NET project initialization by running the setup command, which optionally generates the file to enforce coding styles and maintainability standards.

What is the best way to bootstrap a .NET project for maintainability?

The best way to bootstrap a .NET project for maintainability is to initialize it with predefined quality configurations, seeding `.editorconfig` and `Directory.Build.props` to ensure project readiness and consistent standards.

Do I need any dependencies to initialize .NET project directory structures?

You do not need any dependencies to initialize the .NET project directory structures, as the setup process creates the necessary directories and configuration files without requiring external packages.