Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

.NET Project Setup — measured AI agent skill | DecimalAI

managedcode/project-setup

NewSkillScoreMaintained

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,

codingby managedcode

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/managedcode-project-setup/SKILL.md

decimalai skills pull managedcode-project-setup --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/managedcode-project-setup/SKILL.md https://app.decimal.ai/s/managedcode-project-setup/SKILL.md

Raw file: /s/managedcode-project-setup/SKILL.md ↗ · machine-readable summary at /s/managedcode-project-setup.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 2h ago

Yes — +14% lift+5% tokens0% turns100% of whole cases pass with skill (22/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-05	✗→✓	▲ Improved	7%	0%
case-08	✗→✓	▲ Improved	-61%	0%
case-09	✗→✓	▲ Improved	-52%	0%
case-01	✓→✓	＝ Same ✓	4%	0%
case-02	✓→✓	＝ Same ✓	21%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 8/17/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

managedcode / dotnet-skills

catalog/Platform/Project-Setup/skills/project-setup/SKILL.md

View on GitHub ↗

License MITImported 8/17/2026Version v2Bundled 2 files

Skill contents

references/

SKILL.md

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

Current Upstream Notes

The August 2026 "Build apps with .NET" Learn overview reinforces app-model-first setup: console, web, worker, desktop, mobile, cloud, and AI entry points should drive SDK/template choice.
.NET SDK 10.0.400 is the current 10.0.4xx feature band. It expands file-based app support, adds Microsoft.Testing.Platform --project and --solution selection to dotnet test, accepts @ as the dotnet new option separator, and fixes hardlink and incremental-build paths. Keep global.json, workloads, and CI images explicit for the selected feature band.

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

Want to see if managedcode/project-setup would activate on your phrasing? Try it before you install — no LLM call, no signup.

Other measured skills in the registry, with their headline benchmark lift.