frontend-component-auditor

Auditing Next.js 14 App Router components involves verifying server/client boundaries, TypeScript strictness, data-testid coverage, and Tailwind usage. The auditor checks explicit props types, forbids any, requires explicit return types, and validates cn() helper usage.

Enforcing TypeScript strictness in component reviews requires checking for explicit props types, forbidding any usage, and mandating explicit return types. The auditor flags violations and generates an actionable report for interactive elements like ProductGrid or CheckoutForm.

Yes, the Next.js component auditor checks data-testid coverage for interactive elements. It assesses components like AddToCartButton and ProductImages to ensure test identifiers are present, generating a report on missing coverage.

Yes, you can use the auditor to verify Tailwind CSS class usage and prevent inline styles. It enforces proper Tailwind class usage with the cn() helper and flags inline styles in components like ProductDetail.

To run a component quality audit, execute the auditor on a Next.js component file. It analyzes server/client split, TypeScript strictness, data-testid coverage, and Tailwind usage, then returns an actionable report.

The auditor is limited to Next.js 14 App Router components and focuses on TypeScript strictness, data-testid coverage, and Tailwind usage with the cn() helper. It applies to specific component patterns and may not cover all custom styling or testing frameworks.