ada-dotnet-engineering-refactoring

Replace bare string or double fields with readonly struct types that enforce constraints at construction, such as Ratio clamping to [0,1] or PanelId rejecting null values. Add manual IEquatable for .NET 6, implicit/explicit conversion operators, and a custom JsonConverter for serialization.

Start with domain primitives because they have the widest ripple effect, then API naming and catch tightening, orchestrator extraction, base class extraction, dead field removal, and finally Blazor template extraction. Each phase ends with dotnet build, dotnet test, and dotnet format.

Yes, all patterns are .NET 6 compatible. Use manual readonly struct with IEquatable instead of record struct, and use the RegisterElementRef callback pattern instead of @ref lambdas in Blazor, which .NET 6 does not support.

Apply the regex catalog for bulk fixes of constructor calls, method calls, and property assignments across test files, then run dotnet build and manually patch remaining errors like Assert.Equal comparisons and variable type changes. Finish with a full dotnet test run.

Do not use it for simple bug fixes, single-file cleanup, pre-commit formatting, or one-off mechanical deduplication. It is designed for multi-phase architectural work where the codebase must be handed off to human maintainers, and for non-.NET projects a generic refactoring skill applies instead.

Split it into a thin shell plus partial files organized by responsibility, moving members verbatim with zero behavior or API change. Use a script-based split that handles attributes, XML doc comments, and LF normalization, then verify with dotnet build, test, and format checks.