Split the app primarily by feature, with shared capabilities in core modules: ```text :app # DI root, Compose navigation, navigation guard :feature:login # Login UI/ViewModel and login-specific domain/data code :feature:products # Product-listing UI/ViewModel and product-specific code :feature:cart # Cart UI/ViewModel and cart-specific code :core:ui # Shared Compose design system :core:network # API client and network infrastructure :core:dat...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill android-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Android Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-android-architecture-c3a427f0)More formats (shields.io, HTML) on the badges page.
Split the app primarily by feature, with shared capabilities in core modules:
```text
:app # DI root, Compose navigation, navigation guard
:feature:login # Login UI/ViewModel and login-specific domain/data code
:feature:products # Product-listing UI/ViewModel and product-specific code
:feature:cart # Cart UI/ViewModel and cart-specific code
:core:ui # Shared Compose design system
:core:network # API client and network infrastructure
:core:database # Local persistence infrastructure
```
Keep each feature internally layered: domain (pure Kotlin use cases/models), data (repository implementations and data sources), and UI (ViewModel plus Composables). The UI talks to the ViewModel, the ViewModel calls use cases, and repositories remain behind domain-facing interfaces. Keep feature dependencies deliberate and avoid coupling one feature directly to another; place genuinely shared code in `core`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
