code-structure-cleanup

To refactor duplicated logic into a reusable service layer, identify repeated runtime mechanics across multiple files and extract them into shared service functions while keeping domain policy in the calling component.

Run a code cleanup pass to extract service-layer logic only after a feature is fully working, ensuring the refactor preserves user-facing behavior and keeps diffs minimal.

Extracting a service layer does not change user-facing behavior; it implements the smallest viable service extraction to reduce duplication while validating with tests to ensure functionality remains unchanged.

The best way to reduce code duplication without altering domain policy is to move repeated runtime mechanics into a shared service layer module while keeping all domain-specific rules in the calling route or component.

AI agents create duplicated logic instead of reusing existing functions because they often take the easiest path, generating new functions rather than identifying and refactoring shared runtime mechanics into a common service layer.

Yes, you can use a minimal scoped refactor to extract service-layer functions from working features by moving duplicated runtime mechanics into shared modules and validating unchanged behavior with tests.