What problem does it solve? Adding a new feature to a modularized Android or KMP codebase requires recreating the same layering, DI, navigation, and test wiring every time, and inconsistencies creep in when conventions are applied from memory rather than copied from existing modules. ## Core Features & Use Cases - Convention-First Scaffolding: Inspects existing feature modules to copy module layout, Gradle convention plugins, DI framework (Hilt or Koin), navigation style, and state management patterns before generating anything. - End-to-End Feature Skeleton: Generates the Gradle file, settings include, repository stub, use cases, ViewModel with StateFlow, Composable screen, nav route, DI module, and a passing ViewModel test in compile-safe order. - KMP Support: Places shared repository and use case logic in commonMain while keeping Android UI in the platform module, exposing only a Presenter-style API to iOS. - Use Case: A developer asks to "add an onboarding feature" and receives a complete, buildable :feature:onboarding module wired into the app's NavHost with a green test, ready for real business logic. ## Quick Start Ask the assistant to scaffold a new feature module for onboarding that matches the conventions of the existing feature modules in this repository.
