What problem does it solve? Blazor component libraries that port styled React components (like shadcn/ui) often drift visually from the reference: wrong Tailwind classes, mismatched DOM structure, broken open/close animations, and Blazor re-render races that reset JS-set styles. Manually eyeballing two apps side by side misses subtle computed-style differences and animation timing bugs. ## Core Features & Use Cases - Programmatic CSS diffing: Extracts computed styles from both the BlazeUI demo app and the shadcn/ui reference app using Playwright, then diffs them via the reftest CLI (batch, verify, diff, inspect commands). - Animation trajectory verification: Compares open/close animation behavior between apps and diagnoses Blazor-specific issues like re-render flicker, data-[closed]:hidden killing CSS animations, and close/reopen race conditions. - Root-cause diagnosis workflow: Guides reading Base UI index.parts.ts and primitive sources to decide whether a fix belongs in the headless component, styled template, demo page, or JS module. - Use Case: After porting the shadcn Dialog component to BlazeUI, run verify dialog to find that the backdrop renders before first open and the close animation flickers, then apply the documented _closedRendered guard and cancellable exit animation fixes. ## Quick Start Ask the assistant to run a reference test comparing the BlazeUI dialog component against the shadcn reference app and report any CSS or animation differences.
