feature-based organization
Feature-based organization keeps related implementation close to the capability it serves.
Use this when Changing one feature requires searching many unrelated global folders.
without the term
“To change billing I have to touch components/, hooks/, services/, utils/ and types/. Can you organize things so everything for one feature lives together?”
with the term · How do you ask a model for feature-based organization?
Organize this feature’s components, state, and tests together. Verify imports and behavior, and keep genuinely shared code outside the feature boundary.
What is feature-based organization?
A feature's components, state, API calls, and tests sit in one folder. Only code that several features really share goes in a shared folder.
Why does feature-based organization matter when vibe coding?
A generated directory structure can scatter code that changes together.
How do you do feature-based organization?
Identify the feature boundary and move related code without changing behavior or creating import cycles.
What goes wrong with feature-based organization?
Assuming every internal subfolder is wrong even when the feature remains cohesive.