Feature request: Broader .NET, CLI and UI support
Great project. One improvement I'd love to see is broader support for general .NET development, beyond the current strong ASP.NET/backend focus.
Possible areas:
- General .NET: Generic Host, DI, configuration, logging, async/concurrency, cross-platform development, Native AOT, trimming and single-file publishing.
- CLI / Console:
System.CommandLine, command architecture, exit codes, stdin/stdout, interactive/non-interactive tools and publishing.
- Desktop UI: MVVM, bindings, commands, UI threading, application lifetime, navigation and state management.
- Avalonia: XAML, compiled bindings,
StyledProperty, templates, custom controls, CommunityToolkit.Mvvm, cross-platform behavior, AOT/trimming and packaging.
It could fit nicely into the existing skill/agent model with something like:
dotnet-app-engineer
cli-specialist
desktop-ui-specialist
and optional framework-specific skills such as:
desktop-ui
├── mvvm
├── avalonia
├── wpf
└── maui
Additional /dotnet-init project types such as Console, CLI Tool, Desktop App, Avalonia and Library would also be useful.
Many existing features such as modern-csharp, code review, performance analysis, build fixing and Roslyn integration are already very useful for these projects. Making general .NET a first-class use case would significantly broaden the kit's usefulness.
Feature request: Broader .NET, CLI and UI support
Great project. One improvement I'd love to see is broader support for general .NET development, beyond the current strong ASP.NET/backend focus.
Possible areas:
System.CommandLine, command architecture, exit codes, stdin/stdout, interactive/non-interactive tools and publishing.StyledProperty, templates, custom controls, CommunityToolkit.Mvvm, cross-platform behavior, AOT/trimming and packaging.It could fit nicely into the existing skill/agent model with something like:
and optional framework-specific skills such as:
Additional
/dotnet-initproject types such as Console, CLI Tool, Desktop App, Avalonia and Library would also be useful.Many existing features such as
modern-csharp, code review, performance analysis, build fixing and Roslyn integration are already very useful for these projects. Making general .NET a first-class use case would significantly broaden the kit's usefulness.