What problem does it solve? Setting up a new feature, entity, or widget in a Feature-Sliced Design codebase requires consistent folder structure, correct layer placement, and disciplined public API boundaries. Doing this manually leads to inconsistent layouts, deep cross-slice imports, and violated layer rules. ## Core Features & Use Cases - Layer Selection Guidance: Helps decide whether new code belongs in entities/, features/, or widgets/ based on whether it is a business noun, a user-facing capability, or a layout composition. - Standard Slice Scaffolding: Creates the slice folder with index.ts as the public API plus model/, ui/, api/, and lib/ segments. - Boundary Enforcement Checklist: Verifies no imports from higher layers, no cross-slice deep imports, and a minimal public surface before the slice is done. - Use Case: When asked to "add a feature for user login", it scaffolds features/login/ with a public index.ts, TanStack Query options in api/, and business logic in model/. ## Quick Start Ask the assistant to create a new FSD slice, for example: "add a feature for editing the user profile".
