modular-refactoring-pattern

Refactor long files by extracting constants, helpers, and utilities into separate focused modules. Identify files approaching 300 LOC or showing rising complexity, then move magic numbers into constants/, reusable logic into helpers/, and shared utilities into utils/ directories to reduce duplication and keep individual files under 300 LOC.

Create a modular extraction pattern using dedicated constants/, helpers/, and utils/ directories. Move magic numbers and hardcoded values into constants, isolate complex or repeated logic into helpers, and place generic utility functions in utils. This standard structure enforces <300 LOC per file and complexity under 50.

Extract code when files exceed 300 LOC, exhibit rising complexity, or show repeated logic patterns. Use a decision tree to identify which logic moves to constants, helpers, or utilities. Extracting early prevents duplication buildup and maintains measurable refactoring outcomes including zero duplication and reduced file complexity.

Yes. The refactoring workflow uses a step-by-step approach with minimal disruption to existing code. Start by identifying long files and high-complexity sections, then systematically relocate logic into the constants/, helpers/, and utils/ structure while maintaining functionality and preventing code duplication.

Complexity triggers include file size approaching 300 LOC, cyclomatic complexity exceeding 50, and duplicated logic across multiple locations. This Skill guides extraction decisions using these measurable thresholds to determine when constants, helpers, and utilities should be extracted into separate modules.