anti-duplication

To prevent code duplication, proactively search existing endpoints, components, and services before writing new code to surface exact or close matches. This enforces DRY principles by guiding you to reuse established implementations and maintain consistency across your codebase.

You should extract abstract patterns only after identifying three or more similar code instances during your pre-emptive code search. This threshold ensures refactoring is justified and maximizes reusable pattern consistency without premature abstraction across your models.

The best way to find existing implementations is using a pre-emptive code search that surfaces exact matches, close matches, and reusable patterns. This decision framework guides you to either reuse templates, extend current logic, or document justifications for new code.

Yes, you can justify writing a new component if existing implementations do not meet requirements, but you must document the justification. The search results provide a decision framework to extend existing logic where possible before creating new models.

Pre-emptive code search works for refactoring models and endpoints by automatically scanning the codebase to surface reusable patterns. It enforces consistency by guiding you to reuse existing templates instead of duplicating logic across services.