structure-project-organization

Choose based on scale: small projects use layered structure grouping by type (components, hooks, utils), medium projects use hybrid type-and-feature grouping, and large applications use feature-based modules where each feature folder contains its own components, hooks, and API logic.

Screaming architecture is a feature-based, domain-driven folder structure where directories reflect what the application does rather than its tech stack. Features like auth, products, and cart become self-contained modules, making codebases highly scalable and easy to refactor in isolation.

Use git mv to move files so history is preserved, then update all affected import statements. Follow the workflow: analyze the current structure, propose a new layout, create a migration plan, execute moves, and verify by running tests or builds.

Feature-based structure is overkill for small projects, MVPs, and proof-of-concepts where a simple layered structure is faster to set up. It also requires team discipline to avoid circular dependencies between feature modules.

Web and JavaScript games benefit from separating engine core (loop, physics, renderer), entities (player, enemies), systems (collision, input, audio), scenes (menu, levels), and assets (sprites, sounds, shaders) into distinct top-level directories.