How do I install the Project Setup skill?

Run npx skillmds@latest add managedcode/project-setup-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Setup?

managedcode (@managedcode) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Setup by managedcode — Agent Skill

Name: Project Setup
Rating: 4.666666666666667 (3 reviews)
Author: managedcode

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. USE FOR: creating a new .NET solution or restructuring an existing one; setting up Directory.Build.props, shared package management, or repo-wide defaults; defining project. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

managedcode Updated Sep 22, 2026

File contents

.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

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.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

---name: project-setup-3description: Create or reorganize .NET solutions with clean project boundaries, repeatable SDK settings, and a maintainable baseline for libraries, apps, tests, CI, and local development. USE FOR: creating a new .NET solution or restructuring an existing one; setting up Directory.Build.props, shared package management, or repo-wide defaults; defining project. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.---# .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## Workflow1. 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](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](references/templates.md): `dotnet new` templates for console apps, class libraries, ASP.NET Core APIs, worker services, Blazor, test projects, .NET Aspire, and gRPC services

Frequently asked questions