Core .NET language, SDK, project setup, and platform guidance for modern applications.
Collection hub
23 collections
Browse the catalog by collection
Collections are the browse taxonomy of the catalog. They group related lanes, skills, and agents so you can inspect an area before choosing any install surface.
Collections browse. Bundles install.
Collections are the catalog taxonomy. Bundles are one-command grouped installs built from that taxonomy. They should stay aligned, but they are not the same surface.
Browse surface
Collections
Use collections to navigate the taxonomy, compare related skills and agents, and understand an area before you choose an install flow.
Best when: you want discovery, lane context, and drilldowns rather than one grouped install command.
Install surface
Bundles
Use bundles when you already know the direction and want one dotnet skills install bundle ... command to install a focused multi-skill set.
Best when: you want a ready-made grouped install instead of browsing the full taxonomy first.
Browse the catalog by collection
Each collection has its own page with related skills, linked agents, and direct paths into the catalog.
12
Primary .NET analyzers, formatting, and code-quality guidance without frontend tooling noise.
14
Build graphs, binlogs, modernization, and MSBuild-specific diagnostics for .NET solutions.
Package management, publishing, CPM, and trusted release flows for .NET packages.
Template discovery, authoring, and scaffolding flows for new .NET projects.
Performance, crash analysis, static analysis, and observability signals for production .NET code.
9
ASP.NET Core, Blazor, APIs, gRPC, SignalR, and other browser-facing or service-hosted .NET surfaces.
1
Aspire-specific orchestration, AppHost, and distributed app composition guidance.
Azure Functions hosting, worker-model choice, and serverless execution guidance for .NET.
Long-running background services, daemons, and Generic Host worker patterns.
MAUI, device-specific tooling, and mobile runtime guidance separated from desktop and web.
Mixed reality and spatial-computing guidance that does not belong inside AI or generic UI buckets.
Desktop frameworks, rich-client UI patterns, MVVM, and media-oriented application surfaces.
Linting and browser-side quality tooling that stays separate from .NET analyzers.
16
Mainstream .NET test frameworks, execution, and test-quality guidance for everyday delivery work.
Experimental, mutation, and research-oriented test analysis outside the default testing baseline.
Architecture, visualization, and boundary design guidance for larger .NET systems.
Code review, delivery workflow, governance, and repo-wide engineering process guidance.
5
Persistence, data access, ingestion, and storage-oriented .NET guidance.
Agent frameworks, AI composition, MCP, and provider abstractions for .NET applications.
Distributed runtime patterns and Orleans-centered stateful .NET systems.
4
Explicit legacy-only maintenance surfaces that should not leak into the default modern install path.
Runtime and test migration flows kept separate from active development bundles.