skills.rest
luongnguyenminhan
luongnguyenminhanCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-project-structure

Standardize .NET solution layout with centralized build configuration files.

Updated Feb 17, 2026
Search Tags:#architecture#dotnet#project-structure#sdk-pinning#central-packages#source-link
One-click install
npx skills add https://github.com/luongnguyenminhan/EmployeeDemoCS --skill dotnet-project-structure-luongnguyenminhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-project-structure
Source: https://github.com/luongnguyenminhan/EmployeeDemoCS/tree/main/.github/skills/project-structure
Command: npx skills add https://github.com/luongnguyenminhan/EmployeeDemoCS --skill dotnet-project-structure-luongnguyenminhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the layout of .NET solutions, providing a consistent blueprint for repository structure and build configuration.

Core Features & Use Cases

  • Defines a multi-layer architecture layout (API, Application, Domain, Infrastructure) with clear folder conventions.
  • Includes guidance for central build configuration: Directory.Build.props, Directory.Packages.props, SourceLink integration, and SDK pinning via global.json.
  • Supports scalable solution templates for large teams and multi-project repos, ensuring uniformity across projects.

Quick Start

Apply the modern .NET project structure to a new or existing solution.

Frequently Asked Questions about dotnet-project-structure

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

FAQPage Schema
How do I standardize .NET solution architecture across multiple projects?▼

To standardize .NET solution architecture, apply a multi-layer layout (API, Application, Domain, Infrastructure) with clear folder conventions. This ensures structural consistency and uniformity across all projects within large team repositories.

What is the best way to configure central build properties in a .NET repository?▼

The best way to configure central build properties is using Directory.Build.props and Directory.Packages.props files. This approach centralizes build configuration and package versioning conventions, ensuring uniform builds across the entire solution.

How does SDK pinning work for modern .NET project structures?▼

SDK pinning for .NET projects works by utilizing a global.json file to lock the repository to a specific .NET SDK version. This guarantees reliable, reproducible builds by preventing unexpected SDK version drift across development environments.

Can I apply centralized package management to an existing .NET solution?▼

Yes, you can apply centralized package management to an existing .NET solution. The structure implements Directory.Packages.props to enforce central versioning conventions, seamlessly migrating legacy repositories to a unified package architecture.

Does this .NET project structure support SourceLink integration?▼

Yes, this .NET project structure supports SourceLink integration. It includes specific guidance for configuring SourceLink within the central build properties, enabling reliable source debugging and repository traceability across all standardized projects.

Related Skills

Explore More Software Engineering Skills→
seiggyseiggy
57

dotnet-project-structure

Create a modern .NET solution structure with centralized build and package management.

Community
Intermediate
bbsbotbbsbot
1

dotnet-project-structure

Create a modern .NET project structure with .slnx and centralized configuration.

Community
Advanced
kreuzberg-devkreuzberg-dev
836

cicd-pipeline-standards

Enforce standardized multi-stage CI/CD pipelines using task commands with BUILD_PROFILE=ci.

Official
Advanced
jsamuelsen11jsamuelsen11

project-conventions

Enforce .NET project conventions across multi-project solutions.

Community
Intermediate