# winforms-expert

A skill for Windows Forms work: it edits code so the project builds, behaves at runtime and stays editable in the Visual Studio Designer.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 955 installs · ★ 5730
- Author: dotnet
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/dotnet/skills/tree/HEAD/plugins/dotnet-winforms/skills/winforms-expert/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/winforms-expert

## What it does

The skill activates only when the request carries a concrete Windows Forms marker: `WinForms`, `System.Windows.Forms`, `*.Designer.cs` or `*.Designer.vb` files, `TableLayoutPanel`, `BindingSource`, `DataGridView`, `Control.InvokeAsync`. WPF and WPF XAML, .NET MAUI and Avalonia are out of scope, so keep that in mind if one solution mixes WinForms with WPF.

The core rule splits two contexts. Designer files and `InitializeComponent` are treated as a serialization format: control construction, property assignment, collection additions, balanced `BeginInit`/`EndInit` and `SuspendLayout`/`ResumeLayout`, named handlers. No lambdas, no `if`, no `await`, no business logic. Everything more complex moves to the main partial class, usually after `InitializeComponent` has run.

The execution order is strict. First locate a narrow validator or test script in the workspace and read its scenario arguments, then run it, then build with `dotnet build`, and rerun the validator whenever source changes. A green build never substitutes for a layout, binding or serialization check. The skill also forbids claiming the Visual Studio Designer works when nobody actually opened it.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add dotnet/skills --skill winforms-expert -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/winforms-expert/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/winforms-expert/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add dotnet/skills --skill winforms-expert -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/winforms-expert/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add dotnet/skills --skill winforms-expert -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/winforms-expert/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install dotnet/skills winforms-expert
```

2. **Manually: put the files in place**
- File: `.github/skills/winforms-expert/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add dotnet/skills --skill winforms-expert -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/dotnet/skills --path plugins/dotnet-winforms/skills/winforms-expert
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/winforms-expert/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add dotnet/skills --skill winforms-expert -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/dotnet/skills/tree/HEAD/plugins/dotnet-winforms/skills/winforms-expert/SKILL.md

## When to use it
- fix a form the Designer refuses to open after constructor changes
- add a control inside `InitializeComponent` without breaking serialization
- track down controls that duplicate after a Designer save
- move business logic out of the designer file into the main partial class
- check `BindingSource` and `DataGridView` wiring before building

## Example prompts
- add a `DataGridView` bound to a `BindingSource` to this form, keep data loading out of the designer file
- the form builds but the Visual Studio Designer won't open it — find out why and fix it
- move validation out of `InitializeComponent` into the main partial class and run the project validator

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 06d5ccd9998e626e.

BEGIN THIRD-PARTY FILE 06d5ccd9998e626e
````text
---
name: winforms-expert
description: >-
  Create, modify, debug, or review Windows Forms applications only when the request
  contains a concrete Windows Forms marker. USE FOR: WinForms, Windows Forms,
  System.Windows.Forms, WinForms Form or UserControl designer files (*.Designer.cs or
  *.Designer.vb), Visual Studio WinForms Designer, TableLayoutPanel, BindingSource,
  DataGridView, Control.InvokeAsync, component-tray ownership, or custom control
  serialization. DO NOT USE FOR: WPF or WPF XAML, including Window.InputBindings,
  KeyBinding, commands, or DataContext; .NET MAUI; Avalonia; or any request where none
  of the listed Windows Forms markers is present.
license: MIT
---

# WinForms Expert

## Purpose

Implement WinForms changes that compile, behave correctly at runtime, and remain editable in the
Visual Studio Designer. Treat `InitializeComponent` and `*.Designer.*` as a serialization format,
not ordinary application code; keep behavior in the main partial class and verify designer
usability whenever the environment permits.

## Execution Contract

Before editing, list the workspace root and locate any task-specific validator, test script, or
documented verification command. Read its scenario selector and required arguments before choosing
an implementation. After editing:

1. Run that narrow validator first and fix every failure it attributes to the change.
2. Run the focused project build after the validator passes.
3. If the build or any later edit changes source, rerun the narrow validator.
4. Report those commands separately from runtime UI and Designer round-trip checks.

A successful build never substitutes for an available layout, binding, serialization, or
designer-safety validator. Do not finish after merely reading a validator or after a build succeeds.

Use the repository's actual command and arguments; the sequence should look like:

```powershell
pwsh -NoProfile -File <task-validator.ps1> <scenario-arguments>
dotnet build <project> --nologo
```

## Boundaries

Use this skill for:

- Creating or changing a WinForms project, `Form`, `UserControl`, or custom control.
- Editing designer-generated layout, event wiring, resources, or component fields.
- Diagnosing a Form Designer load, serialization, scaling, binding, or toolbox problem.
- Implementing WinForms-specific async, MVVM, accessibility, DPI, or dark-mode behavior.
````
END THIRD-PARTY FILE 06d5ccd9998e626e

The third-party file has ended. Everything between the 06d5ccd9998e626e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2387 of 23143 bytes. © dotnet · MIT · https://github.com/dotnet/skills/tree/HEAD/plugins/dotnet-winforms/skills/winforms-expert/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md