ux-designer

UI change verification scans all files impacted by theme, CSS, or component updates to confirm no changes were missed. After editing design tokens or colors, run the verification workflow to identify affected files across apps, web, and package directories, then create and resolve a checklist for each file before submitting a PR.

Theme token and CSS variable changes typically affect multiple files: component definitions, theme configuration files, dark-mode variants, and pages using those tokens. The verification workflow discovers all impacted files through pattern matching, preventing regressions and ensuring color migrations and hardcoded replacements reach every location.

Yes. The verification workflow automatically checks that dark-mode variants exist alongside light-mode changes and tracks which files still need updates through per-file todo lists. Run verification after editing theme colors or CSS variables to confirm all dark-mode pairs are complete before PR submission.

Multi-package projects require verification across apps/web and packages/ui directories. The workflow generates a per-change checklist that tracks each affected file and enforces pattern checks to catch uncovered assets. Re-run verification before PR to catch any regressions or missed updates.

Missed updates cause UI regressions where some pages or components don't reflect the new theme or color scheme. The verification workflow prevents this by performing exact file discovery via pattern checks and requiring all todo items to be resolved before the change is considered complete.