add-feature

Scaffolding a feature module with vertical slice architecture generates a standardized file layout under src/features/[name]/. It creates types, data, service, test, and adapter files to maintain consistent architectural boundaries across your project.

The vertical slice workflow for a code skeleton follows a 9-step process: explore, scaffold, implement, test, review, and validate. This produces a ready-to-use feature structure with naming conflict checks and guidance for downstream steps.

Yes, generating feature modules covers both frontend and backend contexts. The scaffolder provides guidance for downstream steps like testing and review in typical frontend and backend modules to ensure consistent architectural boundaries.

The best way to avoid naming conflicts when scaffolding feature modules is the built-in conflict check. It validates new module names against existing ones before creating the file layout under src/features/.

A scaffolded vertical slice feature skeleton includes standard files for types, data, service, test, and adapter components. These are generated under the src/features/[name]/ directory to accelerate development.

You should use a vertical slice module structure when you need to maintain scalable architectural boundaries across growing features. It creates isolated, ready-to-use feature skeletons that prevent cross-module coupling better than traditional layered approaches.