pre-implementation-checklist

To prevent code duplication before implementation, perform a structured pre-implementation review to search for existing patterns and identify canonical locations for types, utilities, and components. This enforces DRY principles before coding begins.

A pre-implementation checklist for DRY patterns is a mandatory review process guiding developers to search for existing solutions, report findings, and plan reuse from canonical locations before writing new code.

To find canonical locations for existing utilities and components, conduct a pattern search across types, utilities, and component directories during the design review phase, then report findings to plan your reuse strategy.

Yes, you can use a pre-implementation review for small software projects because the pattern search and DRY enforcement process applies across projects of any size to prevent duplication and promote reuse.

The best way to plan code reuse during initial scaffolding is to search for existing patterns, report findings, and propose a reuse plan with documentation and test alignment to ensure new features match canonical locations.