/ Annuaire / Playground / claude-android-skill
● Communauté dpconde ⚡ Instantané

claude-android-skill

par dpconde · dpconde/claude-android-skill

Teaches Claude Code to build modern Android apps the Google way — Clean Architecture, Compose, Hilt, Room, Flow, offline-first, multi-module by feature.

A skill that encodes modern Android best practices (mirroring the NowInAndroid reference) into Claude Code: Clean Architecture with UI/Domain/Data layers, MVVM + UDF, Jetpack Compose for UI, Hilt for DI, Room for persistence, Kotlin Flow for reactive streams, Retrofit for networking, and a multi-module feature-first project structure.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

claude-android-skill.replay ▶ prêt
0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : claude-android-skill

Scaffold a new Android app with modern architecture

👤 Android developers starting a greenfield project ⏱ ~60 min intermediate

Quand l'utiliser : You're starting a new app and don't want to make architectural mistakes you'll fix in 6 months.

Déroulement
  1. Ask Claude to scaffold the module structure
    Use claude-android-skill. Scaffold a multi-module Android app called 'HabitTracker' with features: home, tracking, settings. Compose UI, Hilt DI, Room DB, offline-first.✓ Copié
    → Modules :app, :core:database, :core:ui, :feature:home… generated
  2. Add first feature end-to-end
    Implement the tracking feature: data layer with Room entity, domain layer with use cases, UI with Compose and ViewModel. Include unit tests.✓ Copié
    → Files across 3 layers + tests all compile

Résultat : A running app that follows NowInAndroid-style patterns.

Pièges
  • Over-engineering a tiny app into 8 modules — Tell the skill explicitly: 'single-module is fine here' for simple projects
Combiner avec : filesystem · github

Migrate a Fragment/XML screen to Compose

👤 Android teams modernizing legacy screens ⏱ ~45 min intermediate

Quand l'utiliser : You have an XML screen and want Compose without rewriting everything in one go.

Déroulement
  1. Analyze the existing screen
    Here's the Fragment + XML for SettingsScreen. Plan a Compose migration keeping the ViewModel intact.✓ Copié
    → Step plan: wrap in ComposeView, port Views, clean XML
  2. Apply the migration
    Implement step 1 — add ComposeView and move the header to Compose.✓ Copié
    → Hybrid screen works; subsequent steps staged

Résultat : A Compose screen with ViewModel contract preserved.

Pièges
  • State lost during migration — Keep the same ViewModel; only the UI layer changes
Combiner avec : github

Add offline-first support to an online-only feature

👤 Developers whose app breaks without network ⏱ ~90 min advanced

Quand l'utiliser : You have a Retrofit-only feature and want cached / queued behavior.

Déroulement
  1. Introduce Room + repository
    Use claude-android-skill to convert the profile feature to offline-first. Add Room entity, repository returning Flow, and a sync worker.✓ Copié
    → Data layer restructured, repository is the single source of truth
  2. Wire UI to the Flow
    Update ViewModel to collect from the repository Flow; handle loading/empty/error states in Compose.✓ Copié
    → UI works offline on first launch after sync

Résultat : A feature that works in airplane mode.

Pièges
  • Conflict resolution forgotten — Decide the strategy up front: LWW, server-wins, or merged — the skill will prompt you

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

claude-android-skill + github

Open a PR per feature to keep the scaffold reviewable

Generate the home feature and open a GitHub PR with just those files.✓ Copié
claude-android-skill + filesystem

Edit across many modules in one session

Apply the Hilt migration across every :feature:* module.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
scaffold_module_tree app name, feature list Greenfield start 0
generate_feature feature name, data model Adding a new feature 0
migrate_to_compose fragment/xml path Legacy screen modernization 0

Coût et limites

Coût d'exécution

Quota d'API
None from the skill; Android SDK is free
Tokens par appel
Large — scaffold + tests can run 20k+ tokens
Monétaire
Free
Astuce
Scaffold once, then iterate feature-by-feature — avoid 'generate the whole app' prompts

Sécurité

Permissions, secrets, portée

Stockage des identifiants : API keys go in local.properties + BuildConfig, never committed
Sortie de données : None from the skill itself

Dépannage

Erreurs courantes et correctifs

Hilt compile error: missing @HiltAndroidApp

Ensure the Application class is annotated and declared in manifest

Vérifier : grep -r '@HiltAndroidApp' app/src/
Room schema mismatch on migration

Either provide a Migration, or set fallbackToDestructiveMigration in dev

Compose preview won't render

Add the Compose preview dependency and annotate @Preview correctly

Alternatives

claude-android-skill vs autres

AlternativeQuand l'utiliserCompromis
Google's NowInAndroid repoYou just want a reference project to copy fromStatic — doesn't generate code for you

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills