What problem does it solve? Deciding where new code belongs becomes chaotic as React and TypeScript projects grow, leading to tangled imports, cross-feature coupling, and unmaintainable folder layouts. This Skill provides a concrete feature-based architecture with clear placement rules and ESLint enforcement. ## Core Features & Use Cases - Feature-Based Organization: Structures code into self-contained feature modules under src/features with api, components, hooks, stores, types, and utils subfolders. - Unidirectional Import Flow: Enforces shared → features → app dependency direction, with ESLint no-restricted-paths configurations to block cross-feature imports. - Decision Tables & Anti-Patterns: Provides lookup tables for where each code type belongs, plus guidance on avoiding barrel files and shared-folder pollution. - Use Case: When starting a new Next.js dashboard, apply this Skill to scaffold the folder structure, configure path aliases, set up ESLint import restrictions, and create the first feature module as a template. ## Quick Start Ask the AI to design a feature-based folder structure for a new React TypeScript project with ESLint rules preventing cross-feature imports.
