| name | component-feature-architecture |
|---|---|
| description | Use when organizing or reasoning about code layout — deciding where a new piece of code belongs, structuring folders and files, understanding or enforcing the Component-Feature Architecture scheme, or checking which components may import each other. Triggers on "folder structure", "where should this code go", "component", "feature", "code layout", "architecture", "dependencies between modules". Do NOT use for framework-specific APIs, naming conventions, or import ordering. |
A component-first code layout: the project is a collection of components (pieces from which the project is assembled), grouped into features by domain. A component lives at feature/segment/component. File structure is a consequence of the architecture, not the cause — first understand the components and their interaction rules, then the folder layout emerges from that.