components-auditor

To audit React component quality before a PR, review the component against a shared contract, validate the 6-file structure, check Storybook conventions, run visual states protocols, and verify accessibility expectations like focus and contrast.

A component contract audit checks TypeScript prop typing rules, CVA placement, named exports, and Tailwind token usage consistency. It enforces a required 6-file structure and validates specific file responsibilities within the design system.

To verify Storybook conventions, check for required JSDoc documentation and disallow unsupported configuration. Confirm test coverage includes hook logic, DOM behavior, ARIA roles, keyboard interaction, and disabled component states.

Yes, you can use a component audit to review Radix components by validating token usage consistency, running the full visual review protocol for gradients and transitions, and ensuring all visual states and accessibility expectations are met.

The best way to enforce structure during a delegated review is to systematically verify the required 6-file pattern, validate CVA placement and hook responsibilities, and produce a severity-based verdict report using a specified compliance matrix format.