What problem does it solve?
Managing growing codebases becomes unwieldy without a consistent architectural pattern. This Skill enforces a feature-based structure, aligning components, hooks, actions, schemas, types, and public APIs to reduce coupling and improve maintainability.
Core Features & Use Cases
- Feature-based directories: features/{feature-name}/ with components, hooks, actions, schemas, types, db, lib, and a public index.ts to export a stable API.
- Import discipline: barrels and a single public export point to simplify imports and enforce stable public interfaces.
- Public API guarantees: public exports are centralized through index.ts to support safe refactors and clear boundaries.
- Use Case: A team onboarding a new feature can scaffold folders, add exports via the feature's index.ts, and ensure internal modules are not imported directly by consumers.
Quick Start
Create a new feature under features/{name}, add a components folder with reusable UI pieces, create hooks and actions, and expose a public API from features/{name}/index.ts.