Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven…
.NET 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.
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
- Start from the app model and deployment target, then choose the smallest correct SDK and target framework set.
- Use solution folders and project names that reflect bounded contexts or product areas, not temporary implementation details.
- Centralize shared build settings, analyzer rules, nullable context, and package versions where it reduces duplication without hiding important differences.
- Create test projects and CI hooks early so new projects do not drift into unverified templates.
- Prefer project references and composition over circular dependencies or utility dumping grounds.
- Document the local build, test, and run path in repo docs or
AGENTS.mdwhen 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 newtemplates for console apps, class libraries, ASP.NET Core APIs, worker services, Blazor, test projects, .NET Aspire, and gRPC services
Related skills
Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.
Use the Microsoft.Extensions stack correctly across Generic Host, dependency injection, configuration, logging, options, HttpClientFactory, and other shared infrastructure…
Related agents
.NET Build
Build-focused orchestration agent for .NET restore, build, test, packaging, CI failures, diagnostics, and environment drift.
Also works: dotnet agents install build
.NET Router
Broad .NET triage agent that classifies the repo and routes work to the right skills or specialist agents.
Also works: dotnet agents install router