android-jetpack

Review Android Jetpack library usage in Android apps and AOSP builds.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Binh230199/ai --skill android-jetpack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-jetpack
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/android-jetpack
Command: npx skills add https://github.com/Binh230199/ai --skill android-jetpack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement, review, and troubleshoot Android Jetpack integrations without drifting into inconsistent architecture, unsafe lifecycle handling, or brittle background work.

Core Features & Use Cases

  • Room Database: Define entities, DAOs, relations, migrations, and schema-exported local persistence for reactive app data.
  • DataStore: Choose between Preferences and Proto storage, handle corruption safely, and replace SharedPreferences with coroutine-safe settings.
  • WorkManager, Paging, and Lifecycle: Set up reliable background jobs, infinite scrolling lists, and lifecycle-aware Flow collection in Compose or view-based UIs.
  • Use Case: Use this Skill when building an offline-first Android app that syncs data, caches it locally, paginates large result sets, and observes state safely across configuration changes.

Quick Start

Ask for help integrating the specific Jetpack library you are using and include your Android app or AOSP context, then describe the feature, data flow, or bug you want implemented or reviewed.

Frequently Asked Questions about android-jetpack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement schema-exported migrations for Room Database in Android?

Schema-exported migrations in Room require exporting database schema JSON files during the build process to validate and generate migration paths. This ensures your offline-first Android app safely handles local persistence updates without losing reactive app data.

When do I need DataStore instead of SharedPreferences for Android app settings?

You need DataStore instead of SharedPreferences when replacing synchronous disk I/O with coroutine-safe settings storage. DataStore provides Preferences and Proto storage options, handles corruption safely, and supports asynchronous data flow for reactive Android UI observation.

How do I set up lifecycle-aware Flow collection in Android Compose?

Lifecycle-aware Flow collection in Compose requires collecting flows only when the lifecycle is at least started to avoid unnecessary emissions and crashes during configuration changes. This pattern ensures safe observation of state across the Android UI lifecycle without wasting resources.

What is the correct way to configure Paging 3 refresh keys for infinite scrolling?

Paging 3 refresh keys require correctly implementing the load function to return the appropriate adjacent page key based on the loaded items. This ensures your Paging source can recover from refreshes and load subsequent pages seamlessly during infinite scrolling list operations.

How do I ensure unique background work with WorkManager in an offline-first app?

Unique background work with WorkManager requires assigning a unique work name to your OneTimeWorkRequest or PeriodicWorkRequest and specifying an ExistingWorkPolicy. This prevents duplicate background sync jobs from queuing when your offline-first Android app retries failed network operations.

Does this Jetpack integration review cover AOSP builds or only standard Android apps?

This Jetpack integration review covers both standard Android apps and AOSP builds, addressing common implementation and code review scenarios for Room, DataStore, WorkManager, Paging 3, and lifecycle-aware Flow collection across both environments.