dotnet-desktop-setup

Audit .NET desktop projects for UI coupling and generate configuration templates.

8|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/j0ruge/skills_commands_manager --skill dotnet-desktop-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-desktop-setup
Source: https://github.com/j0ruge/skills_commands_manager/tree/main/plugins/dotnet-wpf/skills/dotnet-desktop-setup
Command: npx skills add https://github.com/j0ruge/skills_commands_manager --skill dotnet-desktop-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Configures and audits .NET desktop projects (WinForms, WPF, Avalonia) for Claude Code on Windows, generating or updating CLAUDE.md files, scoped rules, editorconfig, Directory.Build.props, global.json, and pre-commit hooks. It audits existing codebases to detect UI coupling, God classes, and architectural violations, recommending structural refactors and decoupling. Use when you want to standardize project setup and Claude-friendly documentation across multiple desktop projects.

Core Features & Use Cases

  • Automated environment and solution analysis, audit of UI coupling, and project structure
  • Generation and update guidance for CLAUDE.md at global and per-project levels
  • Templates for .editorconfig, Directory.Build.props, global.json, and .claude/rules/
  • Progressive 8-step workflow with non-destructive diffs to existing files
  • References templates and decoupling guidance for WinForms->WPF/Avalonia migrations

Quick Start

Run the 8-step workflow from this skill to audit your project and generate configuration files.

Frequently Asked Questions about dotnet-desktop-setup

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

FAQPage Schema
How do I configure .NET desktop projects for Claude Code automation?

To configure .NET desktop projects for Claude Code automation, run the 8-step workflow to audit UI coupling and generate CLAUDE.md, editorconfig, Directory.Build.props, and global.json templates with non-destructive, diff-based updates.

How do I detect and fix UI coupling in WinForms or WPF applications?

Detect and fix UI coupling in WinForms or WPF applications by auditing existing codebases for God classes and architectural violations, then applying recommended structural refactors and decoupling guidance to enable Claude Code automation.

Does Claude Code work with Avalonia, WPF, and WinForms project structures?

Yes, Claude Code works with Avalonia, WPF, and WinForms project structures. The auditing and configuration workflow scopes to all three desktop frameworks, generating scoped rules and per-project documentation.

What is the best way to standardize .editorconfig and global.json across multiple desktop projects?

The best way to standardize .editorconfig and global.json across multiple desktop projects is to generate consistent templates through an automated workflow that applies non-destructive diffs to existing configuration files.

Can I migrate WinForms projects to WPF or Avalonia while setting up Claude Code?

Yes, you can migrate WinForms projects to WPF or Avalonia while setting up Claude Code. The workflow includes references templates and specific decoupling guidance for framework migrations during the configuration process.

Will configuring Claude Code for my .NET desktop project modify my existing source files?

Configuring Claude Code for your .NET desktop project will not modify your existing source files destructively. The workflow applies non-destructive, diff-based updates to generate configuration files and documentation templates.