What problem does it solve?
Adding new public APIs to WinForms controls involves many easy-to-miss requirements: API proposal issues, PublicAPI file tracking, PropertyStore backing, CodeDOM serialization, design-time attributes, and XML documentation. This Skill codifies all of these rules so contributors ship compliant, review-ready API changes.
Core Features & Use Cases
- API Proposal Workflow: Enforces creating or updating an
api-suggestion issue with background, proposal, usage, alternatives, and risks sections before implementation.
- PublicAPI File Maintenance: Specifies exact Roslyn PublicAPI.Unshipped.txt entry formats, including override tracking (RS0016) and experimental API prefixes.
- WinForms Conventions: Mandates PropertyStore-backed properties, Events-collection delegate storage, ShouldSerialize/Reset patterns, SR.resx resource strings, and XML documentation standards.
- Use Case: When adding a
CornerRadius property to a WinForms control, follow this Skill to produce the property, change event, serialization logic, PublicAPI entries, resource strings, and docs in one compliant pass.
Quick Start
Add a new public property with change notification to an existing WinForms control following the new-control-api conventions.