How do I install the Android skill?

Run npx skillmds@latest add diegosouzapw/android in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Android safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Android?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Android free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Android?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Android by diegosouzapw — Agent Skill

Name: Android
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

Android

Build, review, and refactor Android mobile apps (Kotlin) using modern Android patterns. Use for tasks like setting up Gradle modules, Jetpack Compose UI, navigation, ViewModel/state management, networking (Retrofit/OkHttp), persistence (Room/DataStore), DI (Hilt/Koin), testing, performance, release builds, and Play Store readiness.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

android

Use this skill when working on Android client (大前端 / 移动端) codebases.

Defaults (unless repo dictates otherwise)

Language: Kotlin
UI: Jetpack Compose (if legacy XML exists, follow existing structure)
Architecture: MVVM + unidirectional data flow (UDF)
Async: Kotlin Coroutines + Flow
DI: Hilt if present; otherwise keep consistent with current

Project structure (recommended)

app/: application module (entry, navigation, composition root)
core/: shared utilities and platform abstractions (optional)
data/: API + persistence implementations
domain/: use-cases, business models (pure Kotlin)
feature/<name>/: feature modules or packages (UI + presentation)

Workflow

Establish constraints

Min/target SDK, build system, existing modules.
Compose vs XML, single-module vs multi-module.

Define app flows

Identify screens and navigation graph.
Define state models per screen and their events/actions.

Data layer design

API models vs domain models (mapping boundaries).
Retrofit service interfaces + OkHttp interceptors (auth, logging).
Caching strategy: memory vs disk (Room/DataStore).

UI & state

Compose: keep Composables stateless where possible; state hoisted to ViewModel.
ViewModel exposes StateFlow<UiState> and accepts events/intents.
Handle loading/error/empty states explicitly.

Error handling

Normalize errors (network, auth, validation) to domain-friendly types.
Avoid leaking Retrofit/Room types into UI.

Performance & UX

Avoid recomposition traps; use stable models and remember.
Images: Coil; pagination for long lists; debounce inputs.
Accessibility basics: content descriptions, large text support.

Quality gates

Unit tests for domain and ViewModels.
UI tests where meaningful (Compose testing).
Lint/detekt/ktfmt if configured; keep build green.

Output expectations when making changes

Keep diffs localized; avoid broad refactors unless requested.
Add/adjust tests when changing behavior.
For new features: include navigation entry, UI state contract, and data wiring.

---name: androiddescription: Build, review, and refactor Android mobile apps (Kotlin) using modern Android patterns. Use for tasks like setting up Gradle modules, Jetpack Compose UI, navigation, ViewModel/state management, networking (Retrofit/OkHttp), persistence (Room/DataStore), DI (Hilt/Koin), testing, performance, release builds, and Play Store readiness.---# androidUse this skill when working on Android client (大前端 / 移动端) codebases.## Defaults (unless repo dictates otherwise)- Language: Kotlin- UI: Jetpack Compose (if legacy XML exists, follow existing structure)- Architecture: MVVM + unidirectional data flow (UDF)- Async: Kotlin Coroutines + Flow- DI: Hilt if present; otherwise keep consistent with current## Project structure (recommended)- `app/`: application module (entry, navigation, composition root)- `core/`: shared utilities and platform abstractions (optional)- `data/`: API + persistence implementations- `domain/`: use-cases, business models (pure Kotlin)- `feature/<name>/`: feature modules or packages (UI + presentation)## Workflow1) Establish constraints- Min/target SDK, build system, existing modules.- Compose vs XML, single-module vs multi-module.2) Define app flows- Identify screens and navigation graph.- Define state models per screen and their events/actions.3) Data layer design- API models vs domain models (mapping boundaries).- Retrofit service interfaces + OkHttp interceptors (auth, logging).- Caching strategy: memory vs disk (Room/DataStore).4) UI & state- Compose: keep Composables stateless where possible; state hoisted to ViewModel.- ViewModel exposes `StateFlow<UiState>` and accepts events/intents.- Handle loading/error/empty states explicitly.5) Error handling- Normalize errors (network, auth, validation) to domain-friendly types.- Avoid leaking Retrofit/Room types into UI.6) Performance & UX- Avoid recomposition traps; use stable models and `remember`.- Images: Coil; pagination for long lists; debounce inputs.- Accessibility basics: content descriptions, large text support.7) Quality gates- Unit tests for domain and ViewModels.- UI tests where meaningful (Compose testing).- Lint/detekt/ktfmt if configured; keep build green.## Output expectations when making changes- Keep diffs localized; avoid broad refactors unless requested.- Add/adjust tests when changing behavior.- For new features: include navigation entry, UI state contract, and data wiring.

Frequently asked questions