shared-state-components-auditor

To audit shared UI state components for consistency, run a scan targeting the `src/components` and `src/pages` directories to identify instances of EmptyState, ErrorState, and LoadingSkeleton and check their usage. This ensures a unified user experience through component reuse.

Duplicated empty, error, and loading state UI elements occur when pages implement bespoke designs instead of leveraging shared components. Running a component audit flags these duplicated efforts, ensuring design and functional consistency across the application by enforcing the use of shared state components.

The best way to enforce deduplication of EmptyState and LoadingSkeleton components is to run a scan that flags pages implementing bespoke state UI elements. This verifies all relevant pages are updated to use the existing shared components, maintaining a unified user experience.

You need a project directory structure containing `src/components` and `src/pages` directories. The audit searches specifically within these paths to identify instances of shared state components and verify their consistent usage across the application's frontend pages.

You need to run a UI state component consistency audit after introducing new shared state components. This verifies that all relevant frontend pages are updated to use them, preventing duplicated effort and maintaining a uniform user experience throughout the application.

Yes, you can use this component auditing tool to check ErrorState components in your web application. It scans the codebase to identify instances of shared ErrorState components, alongside EmptyState and LoadingSkeleton, and checks for their consistent usage across pages.