ada-engineering-refactoring

Follow a plan-approve-execute workflow: map all affected files, write a phased plan in docs/refactoring/ with verification criteria per phase, get explicit user approval, then execute each phase with build and test checks. Finish with a whole-project consistency pass against six quality gates.

Mechanical dedup falls short when users reject extract-method style fixes and ask for engineering-level quality, whole-project consistency, or a codebase a new developer can extend naturally. That signal means switching to architecture-first refactoring with quality gates.

Introduce readonly structs with IEquatable<T> (not record struct on .NET 6), then cascade fixes through services, commands, DTOs, Razor files, tests, and demo projects. Use constructor wrapping at call sites, .Value for primitive access, and explicit casts for double-to-Ratio assignments.

Default to silent clamping when arithmetic can produce intermediate out-of-range values or tests construct values outside the range, since throwing breaks test setup and intermediate calculations. Reserve throwing for API boundary inputs where out-of-range indicates a genuine bug.

Common issues include missing @key on re-registering components causing stale state, @ref parameter named 'ref' failing as a C# keyword, delegate calls with strong-typed IDs failing CS1503, and ternary type inference failing between value types and null. Extract repeated templates into child components and inline logic into computed properties.

Skip it for single-file cleanup, pre-commit verification, bug fixes, and small scoped changes, which suit simpler patch workflows. For C#/.NET/Blazor-specific refactors, route through the stack-specific dotnet engineering refactoring skill instead.