dont-repeat-yourself

Avoid code duplication by consulting a centralized inventory of existing services and templates before development. You can reuse pre-built mailer services and welcome-email patterns instead of writing new code from scratch.

Existing reusable patterns include modules for database access, CRUD operations, endpoints, and agent patterns. These canonical components are enumerated in a central repository to ensure consistent codebase maintenance.

Find existing code templates by searching a centralized inventory that catalogs integration code, utilities, and services. This inventory guides developers to extend current modules rather than reinventing them.

Yes, the inventory covers utilities across src/servicios and src/database directories. It maps existing modules and patterns to enforce code reuse and prevent redundant development across these components.

The best way to enforce DRY principles is by maintaining a centralized inventory of services and patterns. It provides canonical templates and requires developers to reuse existing modules before writing new code.

You should consult the code reuse inventory before writing a single line of new code. Reading the inventory first ensures you reuse existing utilities and patterns instead of copying or reinventing them.