rule-frontend-components

You can enforce consistent React component patterns by applying codified frontend guidelines that govern directory structure, TypeScript prop destructuring, and server component defaults to prevent architectural drift across your codebase.

Avoiding barrel index.ts files enforces explicit imports without re-exports, which clarifies dependency graphs and prevents circular dependencies within React component directories and feature subdirectories.

The best way to structure React components is placing general components at the root directory and feature-specific components in dedicated subdirectories, ensuring clear separation of concerns and consistent component organization.

No, you should avoid React.FC usage in TypeScript. Instead, define explicit TypeScript type annotations and use prop destructuring to ensure clear, predictable component prop typing and enforce code quality.

You need client-side wrappers for React server components only when client-side interactivity is required, keeping server components as the default and using promise props for non-blocking data integration.

Yes, you can integrate i18n and USWDS by following established component conventions that provide guard rails through custom hooks and wrappers, ensuring consistent internationalization and design system usage.