scaffold-dotnet

Standardize .NET projects with net10.0, Nullable, ImplicitUsings, and central package management.

1|Updated May 30, 2026
One-click install
npx skills add https://github.com/FixPortal/fixportal-claude-skills --skill scaffold-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-dotnet
Source: https://github.com/FixPortal/fixportal-claude-skills/tree/main/skills/scaffold-dotnet
Command: npx skills add https://github.com/FixPortal/fixportal-claude-skills --skill scaffold-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Apply a consistent set of preferences to new or existing .NET projects to reduce drift and manual reconfiguration.

Core Features & Use Cases

  • Standardizes solution structure with a canonical src/ and tests/ layout.
  • Enforces project defaults (net10.0, Nullable, ImplicitUsings) and central package management.
  • Use Case: When starting a new .NET solution or when normalizing an existing repository to align with team conventions.

Quick Start

Run the scaffold-dotnet skill when creating or normalizing a .NET project to apply the standard preferences

Frequently Asked Questions about scaffold-dotnet

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

FAQPage Schema
How do I enforce a consistent .NET project structure across an existing repository?

To enforce consistent .NET project structure, standardize repositories by applying canonical src/ and tests/ layouts, enabling Nullable and ImplicitUsings, and centralizing package management to reduce manual configuration drift.

What is the best way to scaffold a new .NET solution with standardized conventions?

The best way to scaffold a standardized .NET solution is to automate solution and project creation while enforcing net10.0 framework targets, wiring NodaTime where appropriate, and centralizing package management and solution items.

Does .NET centralized package management work with older target frameworks?

Centralized package management works with your .NET projects, but this standardization enforces net10.0 as the target framework. You must update existing codebases to net10.0 to align with these enforced project defaults.

How can I add new projects to an existing .NET solution while maintaining code style conventions?

You can maintain code style conventions when adding projects to a .NET solution by applying standard preferences that automatically enforce defaults like Nullable, ImplicitUsings, and centralized package management during restructuring.

When should I normalize an existing .NET codebase to align with team conventions?

You should normalize an existing .NET codebase to align with team conventions when you need to reduce drift and manual reconfiguration by applying a consistent set of project preferences, structure layouts, and package management rules.