code-reuse-enforcer

Preventing code duplication involves searching specific directories like `app/components/ui/` and `lib/` for existing components and hooks before creating new implementations. This verifies that you reuse available assets instead of reinventing them.

The best way to find existing custom hooks is to consult a component and hook inventory that lists pre-existing utilities. You can search designated directories like `lib/` to locate and reuse these assets instead of building new ones.

You can extend an existing component by locating it in `app/components/` and wrapping it or adding new props. This follows a USE → IMPROVE → ADD philosophy to avoid redundant code while meeting new requirements.

You should search for existing utilities before writing new code to validate against duplication and maintain code quality. Mandating searches in directories like `lib/` ensures you leverage existing solutions instead of creating redundant implementations.

Enforcing code reuse works with your existing component library by providing an inventory of pre-existing UI elements and hooks. It directs developers to specific directories to find and use these established assets.