skills.rest
jhparktime
jhparktimeCOMMUNITY
Explore all skills by this author →
GitHub

android-architecture

Structure Android projects into UI, Domain, and Data layers with Hilt.

1|2|Updated Jan 25, 2026
Search Tags:#architecture#android#mvvm#modularization#clean-architecture#dependency-injection#hilt
One-click install
npx skills add https://github.com/jhparktime/OnGuard --skill android-architecture-jhparktime
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-architecture
Source: https://github.com/jhparktime/OnGuard/tree/main/.claude/skills/android-architecture
Command: npx skills add https://github.com/jhparktime/OnGuard --skill android-architecture-jhparktime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and maintaining Android applications in a way that minimizes tight coupling and accelerates onboarding by enforcing a layered architecture and DI best practices.

Core Features & Use Cases

  • Three-layer separation: UI, Domain, Data with inward dependencies.
  • Dependency Injection with Hilt: Structured modules and annotated entry points.
  • Modularization guidance: Multi-module layout with core, data, domain, and feature boundaries.
  • Use Case-focused Domain: Encourages UseCases encapsulating business logic.

Quick Start

Create a new Android project and structure it into UI, Domain, and Data layers using Clean Architecture, then configure Hilt for dependency injection and modularize into :app, :core, and :feature modules.

Frequently Asked Questions about android-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure an Android app using Clean Architecture and MVVM?▼

Structure your Android app into UI, Domain, and Data layers using Clean Architecture and MVVM. Enforce inward dependencies so the Domain layer remains independent, utilizing ViewModels for UI logic and Repositories for data access.

What is the best way to modularize a multi-module Android project?▼

Modularize your Android project by splitting it into :app, :core, and :feature modules. This multi-module layout enforces strict boundaries between Data, Domain, and UI layers, minimizing tight coupling and accelerating onboarding.

How do I configure Hilt for dependency injection across Android modules?▼

Configure Hilt for dependency injection by creating structured modules and annotated entry points across your Android modules. This ensures scalable and maintainable DI integration throughout the UI, Domain, and Data layers.

When do I need Use Cases in an Android Domain layer?▼

You need Use Cases in the Android Domain layer when encapsulating business logic separately from UI concerns. Use Cases orchestrate data flow from Repositories to ViewModels, maintaining the inward dependency rule of Clean Architecture.

Why does tight coupling make maintaining Android codebases difficult?▼

Tight coupling makes Android codebases difficult to maintain because changes in one layer directly break others. Enforcing three-layer separation with Clean Architecture and Hilt minimizes this coupling, ensuring a scalable codebase.

Related Skills

Explore More Software Engineering Skills→
cedric-champeixcedric-champeix
1

kotlin-build-kmp-gradle-governance

Review and design Gradle build structure for Kotlin Multiplatform projects.

Community
Advanced
Cure-Consulting-GroupCure-Consulting-Group
1

android-feature-scaffold

Scaffold Android features with Clean Architecture, MVI, Compose, and Hilt.

Official
Advanced
MassimilianoPiliMassimilianoPili

mobile-kotlin

Develops native Android apps with Kotlin using Jetpack Compose, MVVM, Hilt, Room, Retrofit, Coroutines and Flow.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

android-architecture

Enforce MVVM, clean architecture, and Hilt dependency injection in Android projects.

Official
Advanced