feature-module-architect

Colocation groups related TypeScript code—components, hooks, services, types—within a single feature folder at src/features/{feature-name}/. This keeps feature logic together, improves maintainability, and makes dependencies explicit through a public index.ts API.

Use feature-based architecture with standard folders (components, hooks, services, types, utils) under src/features/{feature-name}/, enforcing a 500 LOC per-file limit. This pattern prevents monolithic files, keeps concerns separated, and enables independent feature scaling.

Apply a hard 500 LOC per-file limit across your feature modules. When a file approaches the limit, split functionality into smaller, focused files within the same feature folder and re-export through the public API via index.ts.

Yes. Gather scattered feature code into src/features/{feature-name}/ with standard subdirectories, apply the 500 LOC constraint to force decomposition, and expose only necessary exports through index.ts to maintain a clean public API.

Use feature-based architecture when managing multiple frontend features to avoid tangled dependencies, improve code discoverability, and enforce modularity boundaries. The 500 LOC limit ensures files remain testable and maintainable as codebases grow.

Define exports in each feature's index.ts file, selectively exposing only components, hooks, and utilities meant for cross-feature use. This creates a predictable contract and prevents internal implementation details from leaking to other features.