admin-ui-review

To check admin UI code for accessibility and i18n anti-patterns, review changed files in packages/admin to validate Form.Field usage, heading levels, data-testid presence, and hardcoded strings. This enforces established UI patterns and produces a prioritized findings report.

The best way to enforce consistent UI patterns during a pull request review is to audit the changed files for raw Controller usage and improper form components. This catches anti-patterns early, preventing maintainability regressions across the admin package.

Admin UI code lacks consistency with the established UI kit when developers bypass standardized components like Form.Field and use raw Controller usage. Detecting these deviations during codebase audits helps align typography, layouts, and form fields with the project guidelines.

Yes, you can audit existing packages/admin code for missing data-testids and improper heading levels. Analyzing the codebase produces a prioritized remediation report that highlights accessibility gaps and enforces established UI patterns for improved maintainability.

Yes, the admin UI code review process detects hardcoded strings and missing i18n implementations. It analyzes changed files within packages/admin to identify these anti-patterns, ensuring proper internationalization and preventing UX issues across the interface.

The limitation of automated UI pattern detection in admin code is that it focuses strictly on validating predefined structural patterns like Form.Field usage and data-testid presence. It requires established project guidelines to compare against and does not detect subjective visual design flaws.