claude-android-skill

Why use it

Key features

Clean Architecture: UI / Domain / Data layers with strict boundaries
MVVM + Unidirectional Data Flow
Compose + Hilt + Room + Flow + Retrofit stack
Offline-first architecture baked in
Multi-module by feature — each feature self-contained with a clear API

Live Demo

What it looks like in practice

claude-android-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use claude-android-skill

Scaffold a new Android app with modern architecture

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

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

Flow

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.✓ Copied

→ Modules :app, :core:database, :core:ui, :feature:home… generated
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.✓ Copied

→ Files across 3 layers + tests all compile

Outcome: A running app that follows NowInAndroid-style patterns.

Pitfalls

Over-engineering a tiny app into 8 modules — Tell the skill explicitly: 'single-module is fine here' for simple projects

Combine with: filesystem · github

Migrate a Fragment/XML screen to Compose

👤 Android teams modernizing legacy screens ⏱ ~45 min intermediate

When to use: You have an XML screen and want Compose without rewriting everything in one go.

Flow

Analyze the existing screen

Here's the Fragment + XML for SettingsScreen. Plan a Compose migration keeping the ViewModel intact.✓ Copied

→ Step plan: wrap in ComposeView, port Views, clean XML
Apply the migration

Implement step 1 — add ComposeView and move the header to Compose.✓ Copied

→ Hybrid screen works; subsequent steps staged

Outcome: A Compose screen with ViewModel contract preserved.

Pitfalls

State lost during migration — Keep the same ViewModel; only the UI layer changes

Combine with: github

Add offline-first support to an online-only feature

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

When to use: You have a Retrofit-only feature and want cached / queued behavior.

Flow

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.✓ Copied

→ Data layer restructured, repository is the single source of truth
Wire UI to the Flow

Update ViewModel to collect from the repository Flow; handle loading/empty/error states in Compose.✓ Copied

→ UI works offline on first launch after sync

Outcome: A feature that works in airplane mode.

Pitfalls

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

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied

claude-android-skill + filesystem

Edit across many modules in one session

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

Tools

What this MCP exposes

Tool	Inputs	When to call
scaffold_module_tree	app name, feature list	Greenfield start
generate_feature	feature name, data model	Adding a new feature
migrate_to_compose	fragment/xml path	Legacy screen modernization

Cost & Limits

What this costs to run

API quota: None from the skill; Android SDK is free
Tokens per call: Large — scaffold + tests can run 20k+ tokens
Monetary: Free
Tip: Scaffold once, then iterate feature-by-feature — avoid 'generate the whole app' prompts

Security

Permissions, secrets, blast radius

Credential storage: API keys go in local.properties + BuildConfig, never committed

Data egress: None from the skill itself

Review generated dependencies for version pins — the skill may suggest current-as-of-writing versions.

Troubleshooting

Common errors and fixes

Hilt compile error: missing @HiltAndroidApp

Ensure the Application class is annotated and declared in manifest

Verify: 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