claude-android-ninja

Category: Data & AI | Uploader: Drjacky | Downloads: 0 | Version: v1.0（Latest）

Create production-quality Android applications following Google's official Android architecture guidance with Kotlin, Jetpack Compose, MVVM architecture, Hilt dependency injection, Room 3 local persistence (KSP, SQLiteDriver, Flow/suspend DAOs), and multi-module architecture. Triggers on requests to create Android projects, modules, screens, ViewModels, repositories, or when asked about Android architecture patterns and best practices.

Changelog: Source: GitHub https://github.com/Drjacky/claude-android-ninja

Directory Structure

Current level: tree/master/

📁 .github/
- 📁 ISSUE_TEMPLATE/
  - 📄 bug_report.md 907 B
  - 📄 feature_request.md 1.2 KB
- 📄 FUNDING.yml 15 B
📁 assets/
- 📁 convention/
  - 📁 config/
    
    📄 AndroidCompose.kt 2.3 KB
    
    📄 AndroidInstrumentationTest.kt 613 B
    
    📄 GradleManagedDevices.kt 1.7 KB
    
    📄 Jacoco.kt 4.8 KB
    
    📄 KotlinAndroid.kt 3.7 KB
    
    📄 PrintApksTask.kt 955 B
    
    📄 ProjectExtensions.kt 419 B
  - 📄 AndroidApplicationBaselineProfileConventionPlugin.kt 980 B
  - 📄 AndroidApplicationComposeConventionPlugin.kt 713 B
  - 📄 AndroidApplicationConventionPlugin.kt 1.3 KB
  - 📄 AndroidApplicationJacocoConventionPlugin.kt 945 B
  - 📄 AndroidFeatureConventionPlugin.kt 1.9 KB
  - 📄 AndroidLibraryComposeConventionPlugin.kt 693 B
  - 📄 AndroidLibraryConventionPlugin.kt 2.2 KB
  - 📄 AndroidLibraryJacocoConventionPlugin.kt 925 B
  - 📄 AndroidLintConventionPlugin.kt 1.2 KB
  - 📄 AndroidRoomConventionPlugin.kt 1.3 KB
  - 📄 AndroidTestConventionPlugin.kt 952 B
  - 📄 build.gradle.kts 3.6 KB
  - 📄 DetektConventionPlugin.kt 2.1 KB
  - 📄 FirebaseConventionPlugin.kt 1.4 KB
  - 📄 HiltConventionPlugin.kt 1.0 KB
  - 📄 JvmLibraryConventionPlugin.kt 746 B
  - 📄 KotlinSerializationConventionPlugin.kt 676 B
  - 📄 PlayVitalsReportingConventionPlugin.kt 745 B
  - 📄 PlayVitalsReportingTask.kt 1.7 KB
  - 📄 QUICK_REFERENCE.md 14.8 KB
  - 📄 SentryConventionPlugin.kt 784 B
  - 📄 SpotlessConventionPlugin.kt 1.7 KB
- 📄 detekt.yml.template 15.5 KB
- 📄 libs.versions.toml.template 15.4 KB
- 📄 proguard-rules.pro.template 9.7 KB
- 📄 settings.gradle.kts.template 4.2 KB
📁 references/
- 📄 android-accessibility.md 42.9 KB
- 📄 android-code-coverage.md 4.9 KB
- 📄 android-data-sync.md 72.6 KB
- 📄 android-debugging.md 13.2 KB
- 📄 android-graphics.md 35.6 KB
- 📄 android-i18n.md 27.2 KB
- 📄 android-navigation.md 57.3 KB
- 📄 android-notifications.md 38.8 KB
- 📄 android-performance.md 47.4 KB
- 📄 android-permissions.md 22.9 KB
- 📄 android-security.md 66.4 KB
- 📄 android-strictmode.md 8.3 KB
- 📄 android-theming.md 44.6 KB
- 📄 architecture.md 52.9 KB
- 📄 code-quality.md 8.8 KB
- 📄 compose-patterns.md 120.7 KB
- 📄 coroutines-patterns.md 54.1 KB
- 📄 crashlytics.md 22.0 KB
- 📄 dependencies.md 9.2 KB
- 📄 design-patterns.md 54.8 KB
- 📄 gradle-setup.md 33.2 KB
- 📄 kotlin-delegation.md 24.9 KB
- 📄 kotlin-patterns.md 29.3 KB
- 📄 migration.md 22.4 KB
- 📄 modularization.md 16.5 KB
- 📄 testing.md 69.5 KB
📄 .gitignore 2.5 KB
📄 claude-android-ninja.png 1.5 MB
📄 LICENSE.md 1.0 KB
📄 README.md 12.5 KB
📄 SKILL.md 28.1 KB

SKILL.md

---
name: claude-android-ninja
description: Create production-quality Android applications following Google's official Android architecture guidance with Kotlin, Jetpack Compose, MVVM architecture, Hilt dependency injection, Room 3 local persistence (KSP, SQLiteDriver, Flow/suspend DAOs), and multi-module architecture. Triggers on requests to create Android projects, modules, screens, ViewModels, repositories, or when asked about Android architecture patterns and best practices.
license: Apache-2.0
metadata:
  author: DrJacky
  version: 1.0.0
  documentation: https://github.com/Drjacky/claude-android-ninja
  tags: [android, kotlin, compose, mvvm, hilt, room, room3, datastore, paging, gradle, mobile]
---
# Android Kotlin Compose Development

Create production-quality Android applications following Google's official architecture guidance and best practices.
Use when building Android apps with Kotlin, Jetpack Compose, MVVM architecture, Hilt dependency injection, Room 3, DataStore, Paging 3, or Android multi-module projects.
Triggers on requests to create Android projects, screens, ViewModels, repositories, feature modules, or when asked about Android architecture patterns.


## Quick Reference

| Task                                                                                                                                                                  | Reference File                                                  |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
| Project structure & modules                                                                                                                                           | [modularization.md](references/modularization.md)               |
| Architecture layers, (Domain, Data, UI, Common, ...)                                                                                                                  | [architecture.md](references/architecture.md)                   |
| Compose patterns, Material motion, animation, modifiers, stability                                                                                                    | [compose-patterns.md](references/compose-patterns.md)           |
| Accessibility, TalkBack, label copy, live regions, Espresso a11y checks                                                                                               | [android-accessibility.md](references/android-accessibility.md) |
| Notifications, foreground services, media/audio, PiP, sharesheet                                                                                                      | [android-notifications.md](references/android-notifications.md) |
| Data sync & offline-first patterns                                                                                                                                    | [android-data-sync.md](references/android-data-sync.md)         |
| Material 3 theming, spacing tokens, category fit, dynamic colors                                                                                                      | [android-theming.md](references/android-theming.md)             |
| Navigation3, adaptive navigation, large-screen quality tiers                                                                                                          | [android-navigation.md](references/android-navigation.md)       |
| Kotlin best practices, View lifecycle interop                                                                                                                         | [kotlin-patterns.md](references/kotlin-patterns.md)             |
| Coroutines best practices                                                                                                                                             | [coroutines-patterns.md](references/coroutines-patterns.md)     |
| Gradle, product flavors, BuildConfig, build performance                                                                                                               | [gradle-setup.md](references/gradle-setup.md)                   |
| Testing approach                                                                                                                                                      | [testing.md](references/testing.md)                             |
| Internationalization & localization                                                                                                                                   | [android-i18n.md](references/android-i18n.md)                   |
| Icons, adaptive launcher specs, custom drawing                                                                                                                        | [android-graphics.md](references/android-graphics.md)           |
| Runtime permissions                                                                                                                                                   | [android-permissions.md](references/android-permissions.md)     |
| Kotlin delegation patterns                                                                                                                                            | [kotlin-delegation.md](references/kotlin-delegation.md)         |
| Crash reporting                                                                                                                                                       | [crashlytics.md](references/crashlytics.md)                     |
| StrictMode guardrails                                                                                                                                                 | [android-strictmode.md](references/android-strictmode.md)       |
| Multi-module dependencies                                                                                                                                             | [dependencies.md](references/dependencies.md)                   |
| Code quality (Detekt)                                                                                                                                                 | [code-quality.md](references/code-quality.md)                   |
| Code coverage (JaCoCo)                                                                                                                                                | [android-code-coverage.md](references/android-code-coverage.md) |
| Security, Play Integrity (Standard/Classic), server decode, `requestHash`/`nonce`, tiered policy, remediation; Credential Manager; local root checks as supplementary | [android-security.md](references/android-security.md)           |
| Design patterns                                                                                                                                                       | [design-patterns.md](references/design-patterns.md)             |
| Performance, Play Vitals, optional CI reporting (Play Developer Reporting API), startup, recomposition, jank, battery                                                 | [android-performance.md](references/android-performance.md)     |
| Debugging, Logcat levels, ANR, Gradle error patterns, R8, memory leaks                                                                                                | [android-debugging.md](references/android-debugging.md)         |
| Migration guides (XML, RxJava, Navigation, Compose, Room 2→3)                                                                                                         | [migration.md](references/migration.md)                         |

## Workflow Decision Tree

**[ALWAYS FIRST] Scan Android Developers Changelog**
→ List all filenames in this skill's `references/` folder to build the current scope of topics covered by this skill.
→ Read the `Target SDK` and `Min SDK` values from this skill's `README.md` (badge lines near the top).
→ Fetch the changelog JSON from `https://raw.githubusercontent.com/fornewid/android-developers-changelog/refs/heads/main/pages/changelog.json`.
→ If fetching the changelog JSON fails (URL unreachable, network error, or non-200 response), skip the changelog scan entirely and proceed to the matching workflow step below without comment.
→ Scan the **30 most recent entries** (by `date` field, descending).
→ For each entry, read the `title`, `path`, and `summary` fields to determine relevance.
→ **Include** an entry only if it matches ALL of these criteria:
   - Relates to topics covered by the reference files discovered above.
   - Applies to the project's Target SDK (from README.md) or lower. Ignore entries whose changes are exclusively for behavior changes or features introduced in a higher SDK level.
→ **Exclude** an entry if ANY of these apply:
   - It is solely about RxJava, unless the entry is a migration guide from RxJava to Coroutines.
   - It is solely about Java-only APIs with no Kotlin equivalent or relevance.
   - It covers deprecated View-system patterns that the skill already migrates away from (XML layouts, Fragments for UI, Accompanist), unless the entry is a migration guide.
   - It is about Play Store policy, marketing, or non-development topics.
   - It is about platforms outside Android (Wear OS, Android TV, Android Auto) unless the pattern is universally applicable.
   - It is about cross-platform, KMP, CMP, or KMM, unless the entry covers Android-specific features or guides within a KMP context (e.g., Room 3 KMP with Android-only setup).
   - Its summary indicates only cosmetic documentation changes (formatting, link/URL updates, whitespace) with no substantive guidance or API changes.
→ If relevant entries are found, **briefly summarize** them (1-2 lines each).
→ If an entry looks significant enough to affect current guidance, read its diff by fetching `https://raw.githubusercontent.com/fornewid/android-developers-changelog/refs/heads/main/pages/diffs/{diff_file}` for deeper analysis.
→ After the scan, proceed to the matching workflow step below.
→ If no relevant entries are found, proceed directly without comment.

**Creating a new project?**
→ Start with `assets/settings.gradle.kts.template` for settings and module includes  
→ Start with `assets/libs.versions.toml.template` for the version catalog  
→ Copy all files from `assets/convention/` to `build-logic/convention/src/main/kotlin/`  
→ Create `build-logic/settings.gradle.kts` (see `assets/convention/QUICK_REFERENCE.md`)  
→ Add `includeBuild("build-logic")` to root `settings.gradle.kts`  
→ Add plugin entries to `gradle/libs.versions.toml` (see `assets/convention/QUICK_REFERENCE.md`)
→ Copy `assets/proguard-rules.pro.template` to `app/proguard-rules.pro`
→ Read [modularization.md](references/modularization.md) for structure and module types  
→ Use [gradle-setup.md](references/gradle-setup.md) for build files and build logic  

**Configuring Gradle/build files?**
→ Use [gradle-setup.md](references/gradle-setup.md) for module `build.gradle.kts` patterns  
→ Use [gradle-setup.md](references/gradle-setup.md) → "Build Performance" for optimization workflow, diagnostics, and bottleneck troubleshooting  
→ Copy convention plugins from `assets/convention/` to `build-logic/` in your project  
→ See `assets/convention/QUICK_REFERENCE.md` for setup instructions and examples  
→ Copy `assets/proguard-rules.pro.template` to `app/proguard-rules.pro` for R8 rules  

**Setting up code quality / Detekt?**
→ Use [code-quality.md](references/code-quality.md) for Detekt convention plugin setup  
→ Start from `assets/detekt.yml.template` for rules and enable Compose rules  

**Adding or updating dependencies?**
→ Follow [dependencies.md](references/dependencies.md)  
→ Update `assets/libs.versions.toml.template` if the dependency is missing  

**Adding a new feature/module?**
→ Follow module naming in [modularization.md](references/modularization.md)  
→ Implement Presentation in the feature module  
→ Follow dependency flow: Feature → Core/Domain → Core/Data

**Building UI screens/components?**
→ Read [compose-patterns.md](references/compose-patterns.md) for screen architecture, state, components, modifiers  
→ Use [compose-patterns.md](references/compose-patterns.md) -> State Management -> "Loading and refresh UX" for stable layout during loads and refreshes (avoid full-screen spinners that wipe context)  
→ Use [android-theming.md](references/android-theming.md) for Material 3 colors, typography, and shapes  
→ **Always** align Kotlin code with [kotlin-patterns.md](references/kotlin-patterns.md)  
→ Create Screen + ViewModel + UiState in the feature module  
→ Use shared components from `core/ui` when possible

**Handling State and Events?**
→ Use `StateFlow` for state, `SharedFlow` for events (see [coroutines-patterns.md](references/coroutines-patterns.md))
→ Survive process death with `SavedStateHandle` (see [compose-patterns.md](references/compose-patterns.md))

**Setting up app theme (colors, typography, shapes)?**
→ Follow [android-theming.md](references/android-theming.md) for Material 3 theming and dynamic colors  
→ Use semantic color roles from `MaterialTheme.colorScheme` (never hardcoded colors)  
→ Support light/dark themes with user preference toggle  
→ Enable dynamic color (Material You) for API 31+  

**Writing any Kotlin code?**
→ **Always** follow [kotlin-patterns.md](references/kotlin-patterns.md)  
→ Ensure practices align with [architecture.md](references/architecture.md), [modularization.md](references/modularization.md), and [compose-patterns.md](references/compose-patterns.md)

**Setting up data/domain layers?**
→ Read [architecture.md](references/architecture.md)  
→ Hilt `@Binds`, scopes, and DI anti-patterns: [architecture.md](references/architecture.md) -> Domain Layer -> "Dependency Injection Setup"  
→ Create Repository interfaces in `core/domain`  
→ Create implementations in `core/data` using Room 3/Retrofit/DataStore
→ Use DataStore for simple key-value pairs, Room 3 for complex relational data (`suspend` / `Flow` DAOs, `SQLiteDriver`)

**Implementing Lists and Scrolling?**
→ Use `LazyColumn`/`LazyRow` with stable keys and `contentType` (see [compose-patterns.md](references/compose-patterns.md))
→ For large datasets, use Paging 3 (see [compose-patterns.md](references/compose-patterns.md) -> "Paging 3")

**Handling Navigation?**
→ Use Navigation3 for adaptive navigation (see [android-navigation.md](references/android-navigation.md))
→ Avoid navigation anti-patterns (see [android-navigation.md](references/android-navigation.md) -> "Navigation Anti-Patterns")

**Optimizing Performance?**
→ Follow the Performance Checklist in [android-performance.md](references/android-performance.md)
→ If the user asks for **automated Play Console vitals** (CI/Slack, no Play Console UI), use [android-performance.md](references/android-performance.md) → **Optional: Play Vitals observability (Play Developer Reporting API)**
→ Use `BasicTextField2` for high-frequency text input

**Testing?**
→ Read [testing.md](references/testing.md) for testing philosophy and patterns
→ Use Turbine for testing Flow emissions (see [testing.md](references/testing.md) -> "Testing Flow Emissions with Turbine")
→ Create Repository interfaces in `core/domain`
→ Implement Repository in `core/data`
→ Create DataSource + DAO in `core/data`

**Implementing offline-first or data synchronization?**
→ Follow [android-data-sync.md](references/android-data-sync.md) for sync strategies, conflict resolution, and cache invalidation  
→ Use Room 3 as single source of truth with sync metadata (syncStatus, lastModified)  
→ Schedule background sync with WorkManager  
→ Monitor network state before syncing  

**Setting up navigation?**
→ Follow [android-navigation.md](references/android-navigation.md) for Navigation3 architecture, state management, and adaptive navigation  
→ See [modularization.md](references/modularization.md) for feature module navigation components (Destination, Navigator, Graph)  
→ Configure navigation graph in the app module  
→ Use feature navigation destinations and navigator interfaces  

**Adding tests?**
→ Use [testing.md](references/testing.md) for patterns and examples  
→ Use [testing.md](references/testing.md) → "Screenshot Testing" for Compose Preview Screenshot Testing setup  
→ Keep test doubles in `core/testing`  

**Handling runtime permissions?**
→ Follow [android-permissions.md](references/android-permissions.md) for manifest declarations and Compose permission patterns  
→ Request permissions contextually and handle "Don't ask again" flows  

**Showing notifications or foreground services?**
→ Use [android-notifications.md](references/android-notifications.md) for notification channels, styles, actions, and foreground services  
→ Check POST_NOTIFICATIONS permission on API 33+ before showing notifications  
→ Create notification channels at app startup (required for API 26+)  

**Sharing logic across ViewModels or avoiding base classes?**
→ Use delegation via interfaces as described in [kotlin-delegation.md](references/kotlin-delegation.md)  
→ Prefer small, injected delegates for validation, analytics, or feature flags  

**Adding crash reporting / monitoring?**
→ Follow [crashlytics.md](references/crashlytics.md) for provider-agnostic interfaces and module placement  
→ Use DI bindings to swap between Firebase Crashlytics or Sentry  

**Enabling StrictMode guardrails?**
→ Follow [android-strictmode.md](references/android-strictmode.md) for app-level setup and Compose compiler diagnostics  
→ Use Sentry/Firebase init from [crashlytics.md](references/crashlytics.md) to ship StrictMode logs  

**Choosing design patterns for a new feature, business logic, or system?**
→ Use [design-patterns.md](references/design-patterns.md) for Android-focused pattern guidance  
→ Align with [architecture.md](references/architecture.md) and [modularization.md](references/modularization.md)  

**Measuring performance regressions or startup/jank?**
→ Use [android-performance.md](references/android-performance.md) for Macrobenchmark, Baseline Profiles, and ProfileInstaller setup  
→ Keep benchmark module aligned with `benchmark` build type in [gradle-setup.md](references/gradle-setup.md)  
→ If the user explicitly requests to investigate jank or add custom trace points, use [android-performance.md](references/android-performance.md) for System Tracing (`androidx.tracing`) setup

**Setting up app initialization or splash screen?**
→ Follow [android-performance.md](references/android-performance.md) → "App Startup & Initialization" for App Startup library, lazy init, and splash screen  
→ Avoid ContentProvider-based auto-initialization - use `Initializer` interface instead  
→ Use `installSplashScreen()` with `setKeepOnScreenCondition` for loading state  

**Adding icons, images, or custom graphics?**
→ Use [android-graphics.md](references/android-graphics.md) for Material Symbols icons and custom drawing  
→ Download icons via Iconify API or Google Fonts (avoid deprecated `Icons.Default.*` library)  
→ Use `Modifier.drawWithContent`, `drawBehind`, or `drawWithCache` for custom graphics  

**Creating custom UI effects (glow, shadows, gradients)?**
→ Check [android-graphics.md](references/android-graphics.md) for Canvas drawing, BlendMode, and Palette API patterns  
→ Use `rememberInfiniteTransition` for animated effects  

**Ensuring accessibility compliance (TalkBack, touch targets, color contrast)?**
→ Follow [android-accessibility.md](references/android-accessibility.md) for semantic properties and WCAG guidelines  
→ Provide `contentDescription` for all icons and images  
→ Ensure 48dp × 48dp minimum touch targets  
→ Test with TalkBack and Accessibility Scanner  

**Working with images and color extraction?**
→ Use [android-graphics.md](references/android-graphics.md) → "Image Loading with Coil3" for AsyncImage, SubcomposeAsyncImage, rememberAsyncImagePainter, and Hilt ImageLoader setup  
→ Use [android-graphics.md](references/android-graphics.md) for Palette API and color extraction  

**Implementing complex coroutine flows or background work?**
→ Follow [coroutines-patterns.md](references/coroutines-patterns.md) for structured concurrency patterns  
→ Use appropriate dispatchers (IO, Default, Main) and proper cancellation handling  
→ Prefer `StateFlow`/`SharedFlow` over channels for state management  
→ Use `callbackFlow` to wrap Android callback APIs (connectivity, sensors, location) into Flow  
→ Use `suspendCancellableCoroutine` for one-shot callbacks (Play Services tasks, biometrics)  
→ Use `combine()` to merge multiple Flows in ViewModels, `shareIn` to share expensive upstream  
→ Handle backpressure with `buffer`, `conflate`, `debounce`, or `sample`  

**Need to share behavior across multiple classes?**
→ Use [kotlin-delegation.md](references/kotlin-delegation.md) for interface delegation patterns  
→ Avoid base classes; prefer composition with delegated interfaces  
→ Examples: Analytics, FormValidator, CrashReporter  

**Refactoring existing code or improving architecture?**
→ Review [architecture.md](references/architecture.md) for layer responsibilities  
→ Skim [architecture.md](references/architecture.md) -> "Cross-cutting anti-patterns (quick reference)" for common layering mistakes  
→ Check [design-patterns.md](references/design-patterns.md) for applicable patterns  
→ Follow [kotlin-patterns.md](references/kotlin-patterns.md) for Kotlin-specific improvements  
→ Ensure compliance with [modularization.md](references/modularization.md) dependency rules  

**Debugging crashes, ANRs, or obfuscated stack traces?**
→ Follow [android-debugging.md](references/android-debugging.md) for Logcat, ANR traces, and Compose recomposition debugging  
→ Use [android-debugging.md](references/android-debugging.md) for R8 mapping files and manual de-obfuscation  
→ See [gradle-setup.md](references/gradle-setup.md) for R8 build configuration and keep rules

**Debugging performance issues or memory leaks?**
→ Enable [android-strictmode.md](references/android-strictmode.md) for development builds  
→ Use [android-performance.md](references/android-performance.md) for profiling and benchmarking  
→ Use [android-debugging.md](references/android-debugging.md) for LeakCanary and heap dump analysis  
→ Check [coroutines-patterns.md](references/coroutines-patterns.md) for coroutine cancellation patterns  

**Setting up CI/CD or code quality checks?**
→ Use [code-quality.md](references/code-quality.md) for Detekt baseline and CI integration  
→ Use [gradle-setup.md](references/gradle-setup.md) for build cache and convention plugins  
→ Use [testing.md](references/testing.md) for test organization and coverage  

**Handling sensitive data or privacy concerns?**
→ Follow [crashlytics.md](references/crashlytics.md) for data scrubbing patterns  
→ Use [android-permissions.md](references/android-permissions.md) for proper permission justification  
→ Check [android-strictmode.md](references/android-strictmode.md) for detecting cleartext network traffic  

**Migrating legacy code (LiveData, Fragments, Accompanist, RxJava, Room 2.x)?**
→ Use [migration.md](references/migration.md) for all migration paths (including [Room 2.x → Room 3](references/migration.md#room-2x-to-room-3))  
→ Follow [architecture.md](references/architecture.md) for modern MVVM patterns  

**Adding Compose animations?**
→ Use [compose-patterns.md](references/compose-patterns.md) → "Animation" for `AnimatedVisibility`, `AnimatedContent`, `animate*AsState`, `Animatable`, shared elements  
→ Use `graphicsLayer` for GPU-accelerated transforms (no recomposition)  
→ Always provide `label` parameter for Layout Inspector debugging  

**Using side effects (LaunchedEffect, DisposableEffect)?**
→ Use [compose-patterns.md](references/compose-patterns.md) → "Side Effects" for effect selection guide  
→ `LaunchedEffect(key)` for state-driven coroutines, `rememberCoroutineScope` for event-driven  
→ `DisposableEffect` for listener/resource cleanup, always include `onDispose`  
→ `LifecycleResumeEffect` for onResume/onPause work (camera, media), `LifecycleStartEffect` for onStart/onStop (location, sensors)  

**Working with Modifier ordering or custom modifiers?**
→ Use [compose-patterns.md](references/compose-patterns.md) → "Modifiers" for chain ordering rules and patterns  
→ Use `Modifier.Node` for custom modifiers (not deprecated `Modifier.composed`)  
→ Order: size → padding → drawing → interaction  

**Migrating from Accompanist or deprecated Compose APIs?**
→ Use [migration.md](references/migration.md) for Accompanist, Compose API, Material, Edge-to-Edge, and Room upgrades  
→ See [compose-patterns.md](references/compose-patterns.md) → "Deprecated Patterns & Migrations" for a summary list  

**Optimizing Compose recomposition or stability?**
→ Use [compose-patterns.md](references/compose-patterns.md) for `@Immutable`/`@Stable` annotations  
→ Use [android-performance.md](references/android-performance.md) → "Compose Recomposition Performance" for three phases, deferred state reads, Strong Skipping Mode  
→ Check [gradle-setup.md](references/gradle-setup.md) for Compose Compiler metrics and stability reports  
→ Use [kotlin-patterns.md](references/kotlin-patterns.md) for immutable data structures  

**Working with databases (Room 3)?**
→ Define DAOs and entities in `core/database` per [modularization.md](references/modularization.md); use **`androidx.room3`**, KSP, and **`setDriver(BundledSQLiteDriver())`** on the builder (see `app.android.room` convention)  
→ Use [testing.md](references/testing.md) for in-memory database testing and Room 3 migration tests  
→ Follow [architecture.md](references/architecture.md) for repository patterns  
→ Upgrading from Room 2.x: [migration.md → Room 2.x to Room 3](references/migration.md#room-2x-to-room-3)  

**Need internationalization/localization (i18n/l10n)?**
→ Use [android-i18n.md](references/android-i18n.md) for string resources, plurals, and RTL support  
→ Follow [compose-patterns.md](references/compose-patterns.md) for RTL-aware Compose layouts  
→ Use [testing.md](references/testing.md) for locale-specific testing  

**Implementing network calls (Retrofit)?**
→ Use [architecture.md](references/architecture.md) → "Network Layer Setup" for Retrofit service interfaces, Hilt NetworkModule, and AuthInterceptor  
→ Define API interfaces in `core/network` per [modularization.md](references/modularization.md)  
→ Follow [dependencies.md](references/dependencies.md) for Retrofit, OkHttp, and serialization setup  
→ Handle errors with generic `Result<T>` from [kotlin-patterns.md](references/kotlin-patterns.md)  

**Creating custom lint rules or code checks?**
→ Use [code-quality.md](references/code-quality.md) for Detekt custom rules  
→ Follow [gradle-setup.md](references/gradle-setup.md) for convention plugin setup  
→ Check [android-strictmode.md](references/android-strictmode.md) for runtime checks

**Need code coverage reporting?**
→ Use [android-code-coverage.md](references/android-code-coverage.md) for JaCoCo setup  
→ Follow [testing.md](references/testing.md) for test strategies  
→ Check [gradle-setup.md](references/gradle-setup.md) for convention plugin integration

**Implementing security features (encryption, biometrics, pinning)?**
→ Use [android-security.md](references/android-security.md) for comprehensive security guide  
→ Follow [android-permissions.md](references/android-permissions.md) for runtime permissions  
→ Check [crashlytics.md](references/crashlytics.md) for PII scrubbing and data privacy

**Implementing fraud-resistant or high-value flows (payments, session bootstrap, integrity-gated APIs)?**
→ Read [android-security.md](references/android-security.md): **Modern device trust and abuse resistance**, **Play Integrity API** (prerequisites, Standard vs Classic, server checklist, errors, remediation), **Root and Emulator Detection** (how this fits next to Play Integrity), **Security Checklist**  
→ Ask the engineer for Cloud Console / Play Console steps and the **Google Cloud project number** before wiring client code (see prerequisites in that guide)

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

claude-android-ninja

Directory Structure

SKILL.md

Report

Notice