agentsclimarketplace

Dotnet project setup

Skill Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-project-setup

Teach AI agents modern .NET skills for ASP.NET Core, EF, Blazor, MAUI, and more with a growing community catalog

Install
npx -y skills add Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-project-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create or reorganize .NET solutions with clean project boundaries, repeatable SDK settings, and a maintainable baseline for libraries, apps, tests, CI, and local development.

SKILL.md

2.1 KB, 353 tokens by cl100k_base, as published. Nobody here has run it

.NET Project Setup

Trigger On

  • creating a new .NET solution or restructuring an existing one
  • setting up Directory.Build.props, shared package management, or repo-wide defaults
  • defining project layout for apps, libraries, and test projects

Workflow

  1. Start from the app model and deployment target, then choose the smallest correct SDK and target framework set.
  2. Use solution folders and project names that reflect bounded contexts or product areas, not temporary implementation details.
  3. Centralize shared build settings, analyzer rules, nullable context, and package versions where it reduces duplication without hiding important differences.
  4. Create test projects and CI hooks early so new projects do not drift into unverified templates.
  5. Prefer project references and composition over circular dependencies or utility dumping grounds.
  6. Document the local build, test, and run path in repo docs or AGENTS.md when the workflow is not obvious.

Deliver

  • a coherent solution structure
  • shared build defaults that are easy to reason about
  • starter quality and testing hooks for future work

Validate

  • projects have explicit responsibility boundaries
  • shared MSBuild settings do not accidentally override platform-specific needs
  • a new contributor can build and test the repo without guessing

References

  • patterns.md: solution layout conventions, Directory.Build.props, Directory.Build.targets, Central Package Management, global.json, nuget.config, analyzers, multi-targeting, and source link
  • templates.md: dotnet new templates for console apps, class libraries, ASP.NET Core APIs, worker services, Blazor, test projects, .NET Aspire, and gRPC services

What ships with it: 2 files

24.0 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.