repo-best-practices

To align code generation with repository patterns, identify opportunities to reuse existing registries, constants, and shared shells before creating new abstractions, ensuring generated outputs respect the repo's reuse-first conventions.

Best practices for avoiding code duplication during review involve checking that new implementations prefer config-driven data, extract common logic into feature-local helpers, and reuse existing page shells and components rather than introducing redundant abstractions.

You should extract common logic into shared utilities when code generation tasks produce duplicated implementations, specifically refactoring to leverage existing repo patterns, constants, and pure functions to maintain testability and reduce redundancy.

Make generated code more testable by aligning outputs with config-driven data patterns and extracting logic into pure functions, ensuring the code respects existing repository registries and shared shells while isolating side effects.

You can use repo pattern guidelines to onboard new contributors by demonstrating how to provide small code changes that reuse existing patterns, helping them understand established conventions for config-driven data and feature-local helpers.

The best way to handle code generation for shared shells and registries is to ensure the generation process respects existing repo patterns, avoids duplicating page shells, and provides pure functions for testability across typical codegen tasks.