Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
managedcode avatar

Project Setup

  • 20 installs
  • 466 repo stars
  • Updated July 25, 2026
  • managedcode/dotnet-skills

Helps with ai & agent building tasks.

About

project-setup is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • project-setup
  • AI & Agent Building
  • AI-coding skill

Project Setup by the numbers

  • 20 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #10,442 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/managedcode/dotnet-skills --skill project-setup

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs20
repo stars466
Last updatedJuly 25, 2026
Repositorymanagedcode/dotnet-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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

Current Upstream Notes

  • The current "Build apps with .NET" Learn page reinforces app-model-first setup: console, web, worker, desktop, mobile, cloud, and AI entry points should drive SDK/template choice.
  • .NET SDK 8.0.422 is servicing for the 8.0 line. Keep global.json and CI images explicit when a repo needs that line instead of relying on a newer local SDK.

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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.