cck-project-structure

Standardize .NET solution and project structure with .slnx and central package management.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/s205109/AHKFlowApp --skill cck-project-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cck-project-structure
Source: https://github.com/s205109/AHKFlowApp/tree/main/.claude/skills/cck-project-structure
Command: npx skills add https://github.com/s205109/AHKFlowApp --skill cck-project-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized blueprint for .NET solutions and project structure, ensuring consistent layout and naming across repositories.

Core Features & Use Cases

  • Centralized conventions for solution layout, Directory.Build.props, Directory.Packages.props, and .slnx usage.
  • Clear src/ and tests/ separation with consistent project naming and namespaces.
  • Guidance for onboarding new projects and maintaining global usings and editorconfig usage.

Quick Start

Apply these conventions when setting up a new solution or adding projects to ensure consistent structure.

Frequently Asked Questions about cck-project-structure

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

FAQPage Schema
How do I standardize .NET solution structure to reduce naming drift across repositories?

To standardize .NET solution structure, enforce .slnx as the solution format, use Directory.Build.props for shared properties, and separate projects into src/ and tests/ with consistent naming. This layout reduces setup time and prevents naming drift across repositories.

What is central package management in .NET and how do I set it up?

Central package management in .NET is configuring dependencies via Directory.Packages.props instead of individual project files. You set it up by adopting this file across your src and tests directories to centralize versioning and enforce consistent package references throughout the solution.

How do I configure global usings and shared properties for all projects in a .NET solution?

Configure global usings and shared properties by defining them once in Directory.Build.props. This file is automatically picked up by MSBuild, ensuring shared compilation properties and global using directives apply uniformly across all projects within the solution hierarchy.

Does this .NET project structure convention support the .slnx solution format?

Yes, this .NET project structure convention explicitly enforces .slnx as the standard solution format. It replaces traditional .sln files to provide a cleaner, XML-based solution layout that reduces merge conflicts and simplifies solution management.

When should I use Directory.Build.props and Directory.Packages.props in a .NET solution?

Use Directory.Build.props to define shared MSBuild properties and global usings, and Directory.Packages.props when adopting central package management. Apply both during new solution creation or project addition to ensure consistent configuration across src and tests directories.