Skip to content
cccskills
FreePublished on GitHub

dotnet-project-setup

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.0 KB
  • manifest.json47 B
  • references/patterns.md11.0 KB
  • references/templates.md12.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

.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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

dotnet

Free

Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.

The English summary is being prepared. Showing the original description.

managedcode/PrompterOne45Updated May 9, 2026

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific purpose.

The English summary is being prepared. Showing the original description.

managedcode/PrompterOne45Updated May 9, 2026

Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

The English summary is being prepared. Showing the original description.

managedcode/PrompterOne45Updated May 9, 2026

Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. Use when a repo prefers a modern all-in-one CLI over a larger ESLint plus Prettier style stack.

The English summary is being prepared. Showing the original description.

managedcode/PrompterOne45Updated May 9, 2026

Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices.

The English summary is being prepared. Showing the original description.

managedcode/PrompterOne45Updated May 9, 2026

Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning-as-error policy wired into build and CI.

The English summary is being prepared. Showing the original description.

managedcode/PrompterOne45Updated May 9, 2026

See all skills by managedcode

Report a problem with this skill