Agent skill

android-dev

Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill android-dev --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 21 KB
Bundled scripts: none
Path: skills/android-dev/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

This skill instructs an AI coding agent to guide production-grade Android app development across native, cross-platform, and hybrid stacks. It covers lifecycle aspects from architecture and UI to code quality, testing, error handling, release, and maintenance. It directs decisions on stack selection, project architecture, UI design, best practices, error handling, testing, and build/release configurations.

How it works

  • It presents multiple stack options (Native Kotlin, Native Java, Flutter, React Native, Kotlin Multiplatform, Hybrid) with language, UI choices, key libraries, and references.
  • It prescribes a modular architecture structure (app/ui, presentation, domain, data, di) and a unidirectional data flow.
  • It details architecture patterns per stack (MVVM, MVI, BLoC, Riverpod, etc.) and module organization for large apps.
  • It emphasizes UI/design rules (design system tokens, Jetpack Compose guidelines, accessibility, responsive UI) and navigation approaches across platforms.
  • It provides best practices across languages (Kotlin, Java, Dart, TypeScript), dependency management, and a code review checklist.
  • It outlines error handling strategies, a Kotlin Result/Either pattern, crash reporting, and offline resilience.
  • It defines testing strategies (unit, integration, UI/E2E) with tooling per platform and coverage targets.
  • It covers build, release, and CI/CD considerations, including build variants, Gradle guidance, and staged Play Store release strategy.
  • It includes performance targets (startup time, UI/frame targets, memory management) and profiling recommendations.

When to use it

  • Use when deciding on a tech stack for Android projects.
  • Use when setting up project architecture and UI design systems.
  • Use when aiming for code quality, error handling, and testing strategies.
  • Use when configuring build, CI/CD, and release pipelines.
  • Use when optimizing performance or debugging.

What it can touch

  • It references and prescribes tools and libraries such as Kotlin, Jetpack Compose, Room, Retrofit/Ktor, Hilt, WorkManager, DataStore, Navigation Compose, Provider/Riverpod/Bloc, Dio, Drift/Isar, go_router, Ktor, SQLDelight, Koin, kotlinx.serialization, Napier, Firebase Crashlytics, Sentry, LeakCanary, Espresso, Maestro, Appium, MockWebServer, RTK Query, Zustand, Redux Toolkit, MMKV, and various CI/CD platforms.

Caveats

  • Declared risk: safe
  • License: MIT
  • License and risk are stated; no additional limitations beyond what is described in the skill text.
From the SKILL.md

# Android App Development Skill ## Overview This skill guides production-grade Android and cross-platform (non-iOS) app development following practices used at big tech companies. It covers the entire development lifecycle — architecture, UI, code quality, testing, error handling, release, and maintenance. ## When to Use This Skill - Use when deciding on a tech stack (see §1 Stack Selection) - Use when setting up project architecture (see §2 Architecture) - Use when designing UI, screens, or a design system (see §3 UI & Design) - Use when ensuring code quality, patterns, or APIs (see Best Practices) - Use when implementing error handling or debugging crashes (see §5 Error Handling) - Use when planning testing strategy (see §6 Testing) - Use when configuring build, CI/CD, or release pipelines (see §7 Build & Release) - Use when optimizing performance or memory (see §8 Performance) - Use when debugging or fixing bugs (see §9 Debugging) - Use when following the full development roadmap (see §10 Development Roadmap) - Use when needing deep reference for a stack (see `references/` directory) --- ## §1 Stack Selection Choose based on team, requirements, and platform targets. **Do not rec

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. §1 Stack Selection
  4. Native Android — Kotlin + Jetpack Compose
  5. Native Android — Java + XML Views
  6. Flutter (Dart)
  7. React Native (JavaScript/TypeScript)
  8. Kotlin Multiplatform (KMM / Compose Multiplatform)
  9. Hybrid (Capacitor / Ionic)
  10. Decision Matrix
  11. §2 Architecture
  12. Core Principle: Separation of Concerns
  13. Recommended Architecture: Clean Architecture + MVI/MVVM
  14. Key Architecture Patterns by Stack
Ships with 6 files
  • references/flutter.md
  • references/hybrid.md
  • references/java-android.md
  • references/kmm.md
  • references/native-android.md
  • references/react-native.md
More from agentic-awesome-skills
All skills →
About this skill
What does the android-dev skill do?

Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill android-dev --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going