android-development

Build Android apps with Kotlin, Jetpack Compose, MVVM, Hilt, and Room.

310|42|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/dpconde/claude-android-skill --skill android-development-dpconde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-development
Source: https://github.com/dpconde/claude-android-skill/tree/main
Command: npx skills add https://github.com/dpconde/claude-android-skill --skill android-development-dpconde

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill removes the guesswork from modern Android development by giving Claude a production-ready playbook for building apps with consistent architecture, clean module boundaries, and testable code.

Core Features & Use Cases

  • Architecture Guidance: Follow Clean Architecture patterns across UI, Domain, and Data layers.
  • Compose UI Patterns: Create Route and Screen structures, handle state hoisting, and implement Material 3 theming.
  • Project Scaffolding: Set up multi-module Gradle projects, convention plugins, and feature modules with API and implementation splits.
  • Data and Testing Workflows: Build offline-first repositories, use Room and Flow, and apply test doubles instead of mocking libraries.
  • Use Case: Turn an empty Android project into a scalable feature module with ViewModel, UiState, navigation, repository wiring, and tests.

Quick Start

Ask Claude to create or refactor an Android feature module in your project using the architecture, Compose, Hilt, Room, and modularization patterns defined in this Skill.

Frequently Asked Questions about android-development

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

FAQPage Schema
How do I structure a multi-module Android project with Kotlin and Jetpack Compose?

Structure multi-module Android projects using feature-scoped module boundaries with API and implementation splits, Gradle convention plugins, and Compose Route and Screen patterns to enforce clean architecture across UI, Domain, and Data layers.

What's the best way to set up offline-first data access with Room and Flow in Android?

Set up offline-first Android data access by building repositories with Room and Flow, ensuring unidirectional state flow for reactive UI state without relying on mocking libraries for tests.

How do I implement unidirectional state flow and MVVM with Hilt in an Android app?

Implement unidirectional state flow with MVVM and Hilt by creating ViewModels and UiState objects, wiring feature-scoped repositories, and using Flow-based reactive UI state to handle state hoisting in Compose.

Can I use this approach to refactor an existing Android feature module into Clean Architecture?

Yes, you can refactor existing Android modules into Clean Architecture by applying feature-scoped module boundaries, Hilt dependency injection, Room repositories, and test doubles to establish scalable UI, Domain, and Data layers.

Do I need Gradle convention plugins for modularization in Android development?

Gradle convention plugins are needed to standardize multi-module Android project setups, enforcing consistent build configurations across feature modules with API and implementation splits for clean modularization.