Focused Files

Apply divide and rule: keep every file short, focused, and responsible for one cohesive concern. Break files that contain too many lines or multiple concerns into smaller, clearly named files before they become difficult to maintain. Never inline a cohesive module into a caller or configuration file merely to avoid creating, exporting, mapping, or loading a separate file. When composition or containerization requires an explicit mapping for a new file, add the mapping instead of inlining the code.