create-core-module

To scaffold an Android core module, generate the build.gradle.kts files, repository interfaces, implementation classes, and Hilt dependency injection modules. This enforces architectural consistency and strict dependency rules across your multi-module Gradle project.

Enforcing architecture consistency requires standardized module creation that mandates project-specific dependency directions and naming conventions. By automating the generation of build files and Hilt modules, you eliminate architectural drift and boilerplate overhead when adding new domain components.

Yes, you need Kotlin and Hilt to standardize Android shared library modules. The standardization process specifically generates Kotlin-based build.gradle.kts files and Hilt dependency injection modules to maintain multi-module project integrity and ensure proper dependency injection.

Adding new domain modules causes architectural drift because manual boilerplate creation often ignores strict dependency rules, such as depending on core:common and using DispatcherProvider. Standardized scaffolding prevents this by enforcing project-specific dependency directions and naming conventions automatically.

You need to generate a new core module when adding a data layer for a feature like user-preferences or network-sync. This provides the exact template to maintain your multi-module project integrity and ensures consistent Hilt dependency injection and architectural structure.