review-duplication

Extract the core logic from the new code, hypothesize where similar utilities would live in the project, then search the codebase for structural similarity and matching naming patterns. Delegate deep investigations to sub-agents for open-ended searches.

Check package.json for installed libraries that already provide the functionality, then search utility directories like packages/core/src/utils for existing wrappers. Trace how third-party dependencies are currently used in the project.

Delegate any open-ended investigation, such as semantic comparisons or architectural mapping, to sub-agents to avoid bloating session history. Use direct searches only for simple unambiguous checks like verifying a dependency in package.json.

A good comment identifies the exact file path and symbol to reuse, provides a code snippet showing how to integrate it, and explains the benefit such as consistency or built-in edge case handling.

Yes, the workflow covers UI components by comparing new components semantically against existing ones in component directories and checking styling against theme variables rather than hardcoded values.