b2c-android-create-feature

To scaffold an Android feature module, run the Gradle task with your desired feature name to automatically generate the Screen, ViewModel, Contract, and Navigation stubs. This enforces project conventions and validates feature names during module generation.

Enforcing project conventions during Android feature module creation is handled by validating the feature name and applying structures defined in CLAUDE.md and project-convention.md. This ensures package structures, contracts, and Gradle integration points meet project standards automatically.

Yes, Gradle is required to generate package structures and navigation stubs for Android features. The scaffolding process relies on Gradle-based module generation to validate feature names, check for duplicate modules, and integrate new feature modules into the project.

Validating feature names and checking for duplicate modules is built directly into the Android feature scaffolding process. The automation checks for existing modules and enforces naming conventions before generating the Screen, ViewModel, and Contract file structures.

Android feature module scaffolding fails to integrate when the provided feature name violates project conventions or duplicates an existing module. The automation strictly enforces package naming and Gradle module generation standards defined in project configuration files.