Use when building or assessing Payload UI, changing styles, content, interactions, focus, keyboard behavior or semantics, or working on accessibility tests or WCAG/VPAT evidence.
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Use when a Payload pull request needs a concise visual walkthrough for reviewers.
Use when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails
Use when new translation keys are added to packages to generate new translations strings
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests
Use when UI changes are complete and e2e tests need updating. Analyzes what changed in UI components and systematically finds/fixes affected tests.
Review UI4 CSS migrations for proper token usage. Checks that CSS variables are used instead of hardcoded values.