file-organization

Establish scalable project structures with standardized naming conventions and folder organization patterns. File Names : Folder Names : Variable/Function Names : components/ui/index.ts : ❌ Bad example : tsconfig.json : Usage : #file-organization #project-structure #folder-structure #naming-conventions #utilities - Provides templates for React/Next.js frontends, Node.js/Express backends, and feature-based large-scale applications with clear separation of concerns - Defines naming conventions for files (PascalCase components, camelCase utilities, UPPER_SNAKE_CASE constants), folders (kebab-case or camelCase), and variables (with is/has/can prefixes for booleans) - Includes best practices for path aliases, barrel exports, colocation of related files, and enforcing maximum folder depth to prevent excessive nesting - Covers constraints like avoiding circular dependencies, vague folder names, and deep nesting beyond five levels - New Projects : Initial folder structure design - Project Growth : Refactoring when complexity increases - Team Standardization : Establish consistent structure - Consistency : Entire team uses the same rules - Clear Folder Names : Roles must be explicit - Max Depth : Recommend 5 levels or fewer - Excessive Nesting : Avoid 7+ levels of folder depth - Vague Names : Avoid utils2/, helpers/, misc/ - Circular Dependencies : Prohibit A → B → A references -...