modularization

What problem does it solve?

Modularization prevents files from accumulating mixed responsibilities, reduces cognitive load when navigating the codebase, and stops brittle coupling that becomes expensive to refactor as the project grows.

Core Features & Use Cases

• Single Responsibility Rule: Ensure each file has one reason to change and split UI, logic, and side effects into separate modules.
• Layer Map & Placement: Provide a clear mapping for components/, hooks/, services/, domain/, infra/, utils/, types/, constants/, and schemas/ so every piece of code has a predictable home.
• Naming, Imports, and Splitting Guidance: Standardize naming conventions, import ordering, and thresholds for when to extract code (reasons to split: multiple layers, >150 lines, or multiple distinct responsibilities).
• Feature-Based Organization: Recommend grouping by feature with a public index barrel to expose a minimal API for other features.
• Practical Decision Aid: Offer concrete examples (component vs hook vs service) and a procedure to reorganize messy files safely.

Quick Start

Identify a file that mixes rendering and side effects, extract the UI into a components/ entry, move stateful effects into a hooks/ file, and place API calls in a services/ module.