template-instantiation

Create .NET projects from dotnet new templates with Central Package Management.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill template-instantiation-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-instantiation
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/template-instantiation
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill template-instantiation-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates time wasted on manual, error-prone scaffolding when creating new .NET projects, especially in repos that use Central Package Management (CPM) and require consistent multi-project structure.

Core Features & Use Cases

  • CPM-aware project creation: Instantiates projects in a way that respects Directory.Packages.props and helps avoid stale or conflicting package versions.
  • Validated template parameter workflows: Guides you to inspect template options, preview with --dry-run, and then create with correct framework/auth/AOT settings.
  • Multi-project composition support: Helps scaffold API + tests + libraries and wire references/solution membership after creation.
  • Package template management: Covers installing/uninstalling template packages to ensure the right template set is available.

Quick Start

Ask the skill to create a CPM-safe ASP.NET Core Web API project named MyApi on net10.0 at ./src/MyApi with Individual auth and then build the result.

Frequently Asked Questions about template-instantiation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a .NET project with Central Package Management?

Scaffolding a .NET project with Central Package Management requires instantiating templates that respect Directory.Packages.props to avoid stale package versions. This workflow previews with --dry-run, sets framework and auth parameters, then verifies with dotnet build.

Why does dotnet new break CPM package versions in multi-project solutions?

Manual dotnet new commands can break CPM package versions by introducing conflicting or stale references. Validated template parameter workflows solve this by ensuring workspace consistency and applying CPM version migration guidance after project creation.

Can I use dotnet new templates to scaffold a multi-project API and test solution?

Yes, template instantiation supports multi-project composition for API, tests, and libraries. It scaffolds the projects and wires references and solution membership after creation to ensure a consistent multi-project structure.

What's the best way to manage dotnet new template packages?

The best way to manage dotnet new template packages is through install and uninstall workflows that ensure the correct template set is available. This guarantees validated template parameters are used during project instantiation.

Do I need a dry-run preview before creating .NET projects from templates?

Yes, a --dry-run preview is required before creating .NET projects from templates. It validates template parameters for framework, auth, and AOT settings to prevent workspace inconsistencies before applying CPM version migration.