What problem does it solve? When multiple UI or behavior bugs appear at once, fixing them one by one often exposes new symptoms and never addresses the underlying design flaw. This Skill provides a five-phase methodology to trace symptom clusters to a single architecture-level root cause before writing any code. ## Core Features & Use Cases - Symptom-to-Root-Cause Tracing: Maps each reported bug to its code path, identifies the shared design pattern, and presents the root cause with evidence before any fix is written. - Mandatory SRS Coverage Audit: Produces a requirement table grouping affected specs into directly broken, indirectly affected, and regression-guard categories, verifying every acceptance criterion. - Blazor Interop Anti-Pattern Catalog: Documents recurring pitfalls such as firstRender-coupled registration, boolean _registered flags, @ref inside RenderFragment, and front-end/back-end semantic gaps. - Use Case: A user reports three dock panel bugs — drops rejected, wrong highlight zones, and panels stuck after moving. The Skill traces all three to one drop-target lifecycle flaw and implements a single coherent fix across C# and TypeScript. ## Quick Start Ask the agent to analyze these three related UI bugs together and find their shared architectural root cause before proposing any fix.
