service-development

You can scaffold a new React service by running the project CLI command `new service <serviceName>`, which generates a standardized folder structure under app/features/services. This enforces consistent file roles, naming conventions, and predictable auto-binding.

Maintaining Redux slice injection rules requires following an opinionated service template that separates containers, stores, mappers, and constants. This ensures predictable integration and CLI auto-injection across the React codebase.

To create a React service without a Redux slice, append the `--ns` flag to the CLI scaffolding command. This skips Redux configuration while still generating the standard service containers and constants.

Separating mappers, types, schemas, and constants in app services prevents duplicated logic and inline magic values. This separation enforces predictable file roles and export shapes, enabling reliable CLI auto-injection and consistent code structure.

Yes, you can use this scaffolding template to migrate an existing React feature to the project's template standards. It updates containers, stores, and mappers to ensure predictable integration with the global ServiceInjector.

When preparing services for global registration in the ServiceInjector, you are constrained by enforced export shapes, naming conventions, and Redux injection rules. Deviating from these template conventions breaks predictable CLI auto-injection and code structure consistency.