
litert-runtime
Configures and implements LiteRT (.tflite) on-device inference on Android in Kotlin using the CompiledModel API on CPU and GPU. Use this skill for any Android LiteRT or .tflite task, including Gradle setup, image classification or vision/audio/embedding helpers, TensorBuffer reuse, CPU memory optimization, Bitmap preprocessing, AndroidViewModel GPU-to-CPU fallback with warm-up on a single-thread dispatcher, LiteRT in Google Play services (play-services-litert), migrating from legacy org.tensorflow.lite.Interpreter, GpuDelegate, or play-services-tflite, and latency benchmarking. Don't use for running generative text LLMs with .litertlm files or for Python model conversion.
- Installs
- 184
- Last 24h
- +14
- Trending rank
- #7304
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/android/skills --skill litert-runtime- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads litert-runtime automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
This skill provides step-by-step guidance for building an Android app that runs
a .tflite model with the LiteRT CompiledModel API
(com.google.ai.edge.litert:litert 2.x; source repository) on the CPU or
the GPU, with the runtime bundled in the APK or from Google Play services. Don't
use the deprecated org.tensorflow.lite.Interpreter API. For
open text language models using .litertlm files, suggest the litert-lm
skill.
Prerequisites
- A Kotlin Android project (
minSdkmust be24or higher, as declared by the LiteRT 2.3.0 AARs). - The runtime that Step 1 picks: the Google Play services runtime (
com.google.android.gms:play-services-litert, the default; see LiteRT in Google Play services), or the bundled runtime (implementation("com.google.ai.edge.litert:litert:2.3.0")andimplementation("com.google.ai.edge.litert:litert-gpu:2.3.0")from Google Maven). For the bundled runtime, from 2.3.0 the GPU accelerator is the second artifact: withlitertalone the app builds, andCompiledModel.createwithCompiledModel.Options(Accelerator.GPU)throwsLiteRtExceptionbecause the APK has no GPU accelerator library. WithCompiledModel.Options(Accelerator.GPU, Accelerator.CPU)it doesn't throw: the model runs on the CPU while the app reports the GPU, and only Logcat shows it (GPU accelerator could not be loaded and registered). No manifest entry is needed:litert-api, whichlitertdepends on, declares the OpenCL driver libraries (uses-native-library) in its own manifest. - A verified
.tflitemodel and its input contract (input dimensions, mean, standard deviation, channel order, and tensor layout). For models with a verified recipe, inspect the LiteRT model recipes.
Critical mandates
- Single-thread confinement : One single-thread executor or confined coroutine dispatcher must own the
CompiledModelinstance. Creation, inference, and closing must execute on that same background thread, never on the main thread. - Buffer lifecycle : Allocate
TensorBufferinstances once usingcreateInputBuffersandcreateOutputBuffers, reuse them across inferences, and close all input and output buffers before closing theCompiledModel. - Synchronous timing :
model.runenqueues work on the GPU and returns before GPU execution completes. Always measuremodel.runand output buffer readback (outputs[0].readFloat) together. - Warm-up and exception safety : Execute one warm-up inference inside the helper constructor's
initblock so first-run GPU shader compilation doesn't block the first user interaction, and callcloseincatchbefore rethrowing so neitherCompiledModelnorTensorBufferhandles leak if buffer allocation or warm-up throws. - Runtime choice : Before Step 1, you must read LiteRT in Google Play services and choose the runtime. Use the Google Play services runtime unless the app needs the NPU, custom operators, or a Support library class that this skill can't replace (such as
MetadataExtractor), or also targets devices without Google Play services. Never put both runtimes in the same build variant. - Migration : When the app already uses
org.tensorflow.litecode, you must read the "Migrating from legacy TFLite Interpreter" section in full before you edit any file. Migrated code must not import anyorg.tensorflow.liteclass (includingDataType), every legacy GPU choice (GpuDelegate, or the Support library'sModel.Device.GPU) becomesCompiledModel.Options(Accelerator.GPU, Accelerator.CPU), and an NNAPI choice maps to that same GPU option.
Detailed steps
Step 1: Configure Gradle and place the model file
Search the project for libs.versions.toml, gradle.properties,
app/build.gradle.kts, and any existing org.tensorflow.lite imports before
editing build files. Then pick the runtime:
-
Google Play services runtime (default) : Use it unless one of the bundled runtime cases applies, also when the request doesn't name a runtime. You must read LiteRT in Google Play services now: its dependencies replace the ones in this step, and its
Environmentreplaces theenvironmentproperty of Step 2. Use version17.0.0exactly, and run./gradlew assembleDebug(not--dry-run) after you add it. Switch to the bundled runtime only when that build reportsCould not find com.google.android.gms:play-services-litert:17.0.0, and tell the user, also when the user asked for Google Play services. Never leave the build broken. -
Bundled runtime : Use it only when the app needs the NPU, custom operators, or a Support library class that this skill can't replace (such as
MetadataExtractor), when the app also targets devices without Google Play services, or when the user asks for it.FileUtil,ImageProcessor,TensorImage, andTensorLabeldon't count: replace them as LiteRT in Google Play services describes. For the bundled runtime, configureminSdkand add the LiteRT runtime and GPU accelerator dependencies inapp/build.gradle.kts:android { defaultConfig { minSdk = 24 } }
dependencies { implementation("com.google.ai.edge.litert:litert:2.3.0") implementation("com.google.ai.edge.litert:litert-gpu:2.3.0") }
Place bundled models at app/src/main/assets/model.tflite (AGP stores .tflite
files uncompressed by default). Deliver a model that exceeds the base APK size
limit through Play for On-Device AI as an AI pack, or download it into
context.filesDir (bundletool --local-testing installs AI packs locally
without Google Play). Read an install-time AI pack through AssetManager. Load
a fast-follow or on-demand AI pack or a downloaded file from its on-disk
filePath using CompiledModel.create(filePath, CompiledModel.Options(accelerator), environment) in place of the asset call in
Step 2. Obtain the pack's directory from the AI Delivery library
(com.google.android.play:ai-delivery) using
AiPackManagerFactory.getInstance(context).getPackLocation(name)?.assetsPath(),
which returns null until the pack has finished downloading.
With 2.3.0, nothing is added to gradle.properties: litert 2.3.0 declares
the namespace com.google.ai.edge.litert.impl and its dependency litert-api
2.3.0 declares com.google.ai.edge.litert, so AGP 9.x builds the project. With
2.2.0 or 2.1.6, both libraries declare com.google.ai.edge.litert, and AGP
9.x stops at processDebugMainManifest (AGP 8.x reports it as a warning and
builds); for those two versions, add android.uniquePackageNames=false to
gradle.properties, and remove it when moving to 2.3.0 because it also hides
the same clash between any other two libraries. Excluding litert-api instead
doesn't work: CompiledModel and Accelerator are in litert-api, and the
build then fails at compileDebugKotlin.
Step 2: Implement the inference helper class
Isolate CompiledModel and its TensorBuffer instances in a dedicated
AutoCloseable helper class free of Android UI types:
import android.content.Context
import com.google.ai.edge.litert.Accelerator
import com.google.ai.edge.litert.CompiledModel
import com.google.ai.edge.litert.Environment
import com.google.ai.edge.litert.TensorBuffer
const val INPUT_SIZE = 224 * 224 * 3
private val environment by lazy { Environment.create() }
class Classifier(context: Context, accelerator: Accelerator) : AutoCloseable {
private val model = CompiledModel.create(
context.assets,
"model.tflite",
CompiledModel.Options(accelerator),
environment
)
private val inputs = mutableListOf<TensorBuffer>()
private val outputs = mutableListOf<TensorBuffer>()
init {
try {
inputs += model.createInputBuffers()
outputs += model.createOutputBuffers()
infer(FloatArray(INPUT_SIZE))
} catch (e: Exception) {
close()
throw e
}
}
fun infer(input: FloatArray): FloatArray {
inputs[0].writeFloat(input)
model.run(inputs, outputs)
return outputs[0].readFloat()
}
override fun close() {
(inputs + outputs).forEach { it.close() }
model.close()
}
}
Accelerator.CPU requires nothing from the device. Accelerator.GPU compiles
the graph for the GPU; when the GPU can't execute the model, the constructor
throws LiteRtException (from create for an operator the GPU doesn't support,
and on the Android emulator from create or from buffer allocation). A missing
asset or a file that isn't a valid model also throws LiteRtException from
create.
The buffers are created once with the model, reused for every inference, and
closed before the model. One Environment serves every model in the process and
stays open, so LiteRT loads the GPU accelerator library once rather than on
every create call. The constructor ends with one warm-up inference (the first
GPU run includes shader compilation) and closes the model and its buffers if any
step in init throws. INPUT_SIZE is the model's input element count:
writeFloat throws on a longer array and writes a shorter one without an error,
so a wrong size produces an incorrect result. For int8 or uint8 tensors, use
writeInt8 and readInt8 on TensorBuffer instead of writeFloat and
readFloat.
When memory matters, use the following options:
-
Load from a path :
create(context.assets, ...)keeps a copy of the asset's bytes in the native heap while the model is open. Copy the asset once intocontext.noBackupFilesDir(a downloaded or AI pack file is already on disk) and callcreate(filePath, ...)so the file is mapped and reclaimable. Version the staged filename, bump the version when the bundled model changes, and delete the previous version's file. Copy to a temporary file and rename it so a copy interrupted by process death is never loaded:import android.content.Context import com.google.ai.edge.litert.Accelerator import com.google.ai.edge.litert.CompiledModel import java.io.File
fun stageModelAsset( context: Context, assetName: String = "model.tflite", version: String = "v1" ): File = File(context.noBackupFilesDir, "$version-$assetName").also { file -> if (!file.isFile) { context.noBackupFilesDir.listFiles()?.forEach { if (it.name.endsWith("-$assetName")) it.delete() } val tmp = File("${file.path}.tmp") context.assets.open(assetName).use { input -> tmp.outputStream().use { output -> input.copyTo(output) } } check(tmp.renameTo(file)) } }
fun memoryOptions( context: Context, accelerator: Accelerator = Accelerator.CPU, assetName: String = "model.tflite", version: String = "v1" ): CompiledModel.Options = CompiledModel.Options(accelerator).apply { val prefix = "$assetName-" val cache = File(context.codeCacheDir, "$prefix$version.xnnpack_cache") context.codeCacheDir.listFiles()?.forEach { if (it.name.startsWith(prefix) && it.name.endsWith(".xnnpack_cache") && it != cache) { it.delete() } } cpuOptions = CompiledModel.CpuOptions( numThreads = 4, xnnPackFlags = 0x23, xnnPackWeightCachePath = cache.path ) }
-
Weight cache (
xnnPackWeightCachePath): Written on the first load (~1x an FP32 or ~2x an FP16 model's file size) and mapped on later loads, moving packed FP32 weights off the heap. Version the cache filename and delete outdated caches. -
Transient indirection buffer (
xnnPackFlags = 0x23) : Default0x3plus flag0x20, replacing per-operator convolution pointer tables with one shared buffer (byte-identical outputs, ~1% latency overhead at 4 threads, ~3% single-threaded). Because the value replaces the default,0x20alone leavesint8anduint8operators to fallback kernels.cpuOptionsis ignored on the GPU. -
Close after a task: Closing frees the runtime workspace; recreating with a warm cache takes ~20 ms, whereas the first inference after any load pays a full warm-up run, so close when the next use isn't imminent.
Step 3: Wire the ViewModel and Compose screen
Drive the helper from a single-thread executor inside an AndroidViewModel, and
fall back to Accelerator.CPU when GPU compilation fails:
import android.app.Application
import androidx.lifecycle.AndroidViewModel
import com.google.ai.edge.litert.Accelerator
import com.google.ai.edge.litert.LiteRtException
import java.util.concurrent.Executors
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.SupervisorJob
import kotlinx.coroutines.asCoroutineDispatcher
import kotlinx.coroutines.cancel
import kotlinx.coroutines.flow.MutableStateFlow
import kotlinx.coroutines.flow.StateFlow
import kotlinx.coroutines.flow.asStateFlow
import kotlinx.coroutines.flow.update
import kotlinx.coroutines.launch
data class UiState(
val ready: Boolean = false,
val accelerator: Accelerator = Accelerator.CPU,
val result: List<Float>? = null,
val error: String? = null
)
class MainViewModel(app: Application) : AndroidViewModel(app) {
private val executor = Executors.newSingleThreadExecutor()
private val scope = CoroutineScope(
SupervisorJob() + executor.asCoroutineDispatcher()
)
private var classifier: Classifier? = null
private val _uiState = MutableStateFlow(UiState())
val uiState: StateFlow<UiState> = _uiState.asStateFlow()
fun load(preferred: Accelerator = Accelerator.GPU) {
scope.launch {
if (classifier != null) return@launch
val appContext = getApplication<Application>()
val selected = try {
classifier = Classifier(appContext, preferred)
preferred
} catch (e: LiteRtException) {
if (preferred != Accelerator.CPU) {
try {
classifier = Classifier(appContext, Accelerator.CPU)
Accelerator.CPU
} catch (cpuError: LiteRtException) {
_uiState.value = UiState(error = cpuError.message)
return@launch
}
} else {
_uiState.value = UiState(error = e.message)
return@launch
}
}
_uiState.value = UiState(ready = true, accelerator = selected)
}
}
fun classify(input: FloatArray) {
scope.launch {
try {
classifier?.infer(input)?.let { result ->
_uiState.update {
it.copy(result = result.toList(), error = null)
}
}
} catch (e: LiteRtException) {
_uiState.update { it.copy(error = e.message) }
}
}
}
override fun onCleared() {
scope.launch { classifier?.close() }.invokeOnCompletion {
scope.cancel()
}
executor.shutdown()
}
}
One single-thread executor owns the model: creation, inference, and closing
execute only on it, never on the main thread. The ViewModel keeps its own
scope because viewModelScope is canceled before onCleared runs, so a close
launched there wouldn't run; onCleared cancels scope once close completes.
load is a no-op when a model is already loaded across configuration changes; a
failed load leaves classifier null. classify reports any
LiteRtException (in package com.google.ai.edge.litert) in error and keeps
the model.
The following Compose screen takes the picture (bitmap) from the photo picker
or CameraX and runs preprocess in the click handler (a few milliseconds for
224x224; move preprocess onto the executor for images exceeding 224x224).
viewModel and collectAsStateWithLifecycle come from
androidx.lifecycle:lifecycle-viewmodel-compose and
androidx.lifecycle:lifecycle-runtime-compose:
import android.graphics.Bitmap
import androidx.compose.foundation.layout.Column
import androidx.compose.material3.Button
import androidx.compose.material3.Text
import androidx.compose.runtime.Composable
import androidx.compose.runtime.LaunchedEffect
import androidx.compose.runtime.getValue
import androidx.lifecycle.compose.collectAsStateWithLifecycle
import androidx.lifecycle.viewmodel.compose.viewModel
import com.google.ai.edge.litert.Accelerator
@Composable
fun MainScreen(
bitmap: Bitmap,
viewModel: MainViewModel = viewModel()
) {
val state by viewModel.uiState.collectAsStateWithLifecycle()
LaunchedEffect(Unit) { viewModel.load(Accelerator.GPU) }
Column {
state.error?.let { Text(it) }
Button(
onClick = { viewModel.classify(preprocess(bitmap)) },
enabled = state.ready
) {
Text("Run (${state.accelerator})")
}
state.result?.let { scores ->
Text("Top class: ${scores.indices.maxBy { i -> scores[i] }}")
}
}
}
Step 4: Preprocess inputs to match the model contract
Convert the Bitmap into the model's input with preprocess. Match the
model's exact input dimensions, normalization mean and standard deviation,
channel order, and memory layout (this example uses NHWC, RGB, scaled to
-1.0..1.0). Mismatched mean or std values produce corrupted predictions
that look like a broken model:
import android.graphics.Bitmap
fun preprocess(
bitmap: Bitmap,
size: Int = 224,
mean: Float = 127.5f,
std: Float = 127.5f
): FloatArray {
val scaled = checkNotNull(
Bitmap.createScaledBitmap(bitmap, size, size, true)
.copy(Bitmap.Config.ARGB_8888, false)
)
val pixels = IntArray(size * size).also {
scaled.getPixels(it, 0, size, 0, 0, size, size)
}
val out = FloatArray(size * size * 3)
pixels.forEachIndexed { i, p ->
out[i * 3] = ((p shr 16 and 0xFF) - mean) / std
out[i * 3 + 1] = ((p shr 8 and 0xFF) - mean) / std
out[i * 3 + 2] = ((p and 0xFF) - mean) / std
}
return out
}
The scaled bitmap is copied to Bitmap.Config.ARGB_8888 because ImageDecoder
returns Bitmap.Config.HARDWARE bitmaps by default on Android 9 and higher
(including from a photo picker Uri), scaling preserves that config, and
getPixels can't read HARDWARE bitmaps; the copy is of the 224x224 scaled
bitmap rather than the full image. Scaling doesn't preserve the aspect ratio;
crop first if the model requires center cropping. An audio or embedding model
replaces preprocess with its own input encoding and keeps the inference class.
Step 5: Verify output on a physical device
Run the app on a physical device that runs Android from Android Studio. Compare
the app's output with the model's reference output for one fixed input on
Accelerator.CPU first and then on Accelerator.GPU; when verifying model
outputs on a physical device, you must follow device verification.
Migrating from legacy TFLite Interpreter
An existing app on org.tensorflow.lite.Interpreter (from
org.tensorflow:tensorflow-lite* or from com.google.ai.edge.litert:litert
1.x) moves to the CompiledModel code of Steps 1 to 5 in seven steps, in this
order. Before you change any file of an
existing app, you must read migration, which gives the commands and code
for each step. An app on the Interpreter API in Google Play services
(play-services-tflite-java) follows LiteRT in Google Play services
instead:
- Find the runtime: Read the build files and the resolved dependencies, and note the delegate, the thread count, and the Support library classes that the app uses.
- Capture a golden output first : While the legacy runtime is still in the project, record the app's output for one fixed input on the CPU. This step needs a device or an emulator. Run the capture test with
am instrument, notconnectedDebugAndroidTest, which uninstalls the app and deletes the file. - Swap the dependencies : Delete every legacy artifact line (never leave it commented out) and add the dependencies of the runtime that Step 1 picks: by default those of LiteRT in Google Play services, with the same fallback to the bundled runtime when Gradle can't find
play-services-litert. On the Play services runtime, replace the Support library classes as LiteRT in Google Play services describes. On the bundled runtime, an app keeps them withcom.google.ai.edge.litert:litert-support:2.3.0, with the packageorg.tensorflow.lite.supportrenamed tocom.google.ai.edge.litert.support(LiteRT Support migration guide). - Replace the delegates :
GpuDelegatebecomesCompiledModel.Options(Accelerator.GPU, Accelerator.CPU), so the CPU runs the operators that the GPU doesn't support. An NNAPI choice in the app maps to the same GPU option, not toAccelerator.CPUalone or to an NPU accelerator.setNumThreads(n)becomes new CPU options withcpuOptions = CompiledModel.CpuOptions(numThreads = n). - Rewrite the inference code : Replace
InterpreterandFileUtil.loadMappedFilewith theClassifierhelper of Step 2, created and run only on the single-thread executor of Step 3, never in a constructor that the main thread calls. When no caller retries on the CPU as in Step 3, create the helper's GPU option with the CPU as a second accelerator (CompiledModel.Options(Accelerator.GPU, Accelerator.CPU)). - Verify in two stages: The build passes and the searches for legacy references print nothing; then the migrated output matches the golden output on a device.
- Report what changed and what didn't migrate : When the app used NNAPI, tell the user that it now runs on the GPU with the CPU as a second accelerator, which changes the speed and the numerical results of a quantized model that ran on a DSP or an NPU before; point them to NPU acceleration with LiteRT for the NPU. Tell the user about the TensorFlow Lite Task Library, C++ modules, and Select TensorFlow operators, which this skill doesn't migrate.
Migration mandates that apply to every migrated app:
- No
org.tensorflow.liteimports : Migrated code must not import anyorg.tensorflow.liteclass, includingorg.tensorflow.lite.DataType; the LiteRT artifacts keep these classes only for backward compatibility. Replace Support calls that needDataType(TensorImage(DataType.FLOAT32),TensorBuffer.createFixedSize, andTensorLabel) withpreprocessof Step 4, theCompiledModelbuffers, and labels paired with the output scores. Remove every existingorg.tensorflow.liteimport line, not only the ones that you add.
Antipatterns
- Never create, run, or close
CompiledModelon the Android main thread. - Never allocate new
TensorBufferinstances on every inference call; failing to close per-frameTensorBufferobjects leaks C++ heap memory. - Never benchmark
model.runwithout including output buffer readback (outputs[0].readFloat). - Never mix
org.tensorflow:tensorflow-lite*artifacts (such asorg.tensorflow:tensorflow-lite-support) withcom.google.ai.edge.litert:*artifacts; both ship theorg.tensorflow.lite.*classes and cause duplicate class build failures. - Never use
Accelerator.GPUon LiteRT 2.3.0 without adding thecom.google.ai.edge.litert:litert-gpu:2.3.0dependency alongsidecom.google.ai.edge.litert:litert:2.3.0; with the CPU as a second accelerator, the model silently runs on the CPU. - Never set
xnnPackFlags = 0x20on its own to get the transient indirection buffer; the value replaces the runtime's default0x3, so pass0x23.
Checklist
- [ ] Is
minSdkset to24or higher and are bothcom.google.ai.edge.litert:litert:2.3.0andcom.google.ai.edge.litert:litert-gpu:2.3.0added inapp/build.gradle.kts? - [ ] Are all legacy
org.tensorflow:tensorflow-lite*dependencies andorg.tensorflow.lite.*imports removed? - [ ] Do
CompiledModel.create,model.run, andcloseall execute on the same single-thread background dispatcher? - [ ] Are
TensorBufferinstances allocated once, reused across calls, and closed beforemodel.close, including wheninitor warm-up throws? - [ ] Does
loadexecute one warm-up inference and fall back toAccelerator.CPUifAccelerator.GPUthrowsLiteRtException? - [ ] Does the project compile with
./gradlew assembleDebug? - [ ] If memory matters, is the model created from a path with a versioned weight cache and
xnnPackFlags = 0x23on the CPU, and closed after a task when the next use isn't imminent?
FAQ
What does the litert-runtime skill do?
Configures and implements LiteRT (.tflite) on-device inference on Android in Kotlin using the CompiledModel API on CPU and GPU. Use this skill for any Android LiteRT or .tflite task, including Gradle setup, image classification or vision/audio/embedding helpers, TensorBuffer reuse, CPU memory optimization, Bitmap preprocessing, AndroidViewModel GPU-to-CPU fallback with warm-up on a single-thread dispatcher, LiteRT in Google Play services (play-services-litert), migrating from legacy org.tensorflow.lite.Interpreter, GpuDelegate, or play-services-tflite, and latency benchmarking. Don't use for running generative text LLMs with .litertlm files or for Python model conversion.
How do I install litert-runtime?
Run npx skills add https://github.com/android/skills --skill litert-runtime in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/litert-runtime/ (personal) or .claude/skills/litert-runtime/ (project).
Which AI agents can use litert-runtime?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is litert-runtime safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains litert-runtime?
It is published by android in android/skills. It has 184 recorded installs.
More from android/skills
navigation-3
android/skills
Learn how to install and migrate to Jetpack Navigation 3, and how to implement features and patterns such as deep links, multiple backstacks, scenes (dialogs, bottom sheets, list-detail, two-pane, supporting pane), conditional navigation (such as logged-in navigation versus anonymous), returning results from flows, integration with Hilt, ViewModel, Kotlin, and view interoperability.
edge-to-edge
android/skills
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
r8-analyzer
android/skills
Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use this skill when developers want to optimize their Android app's size, remove redundant or overly broad keep rules, or troubleshoot ProGuard configurations. Don't use for general Gradle build errors, Compose UI performance, or runtime CPU profiling.
android-cli
android/skills
Provides instructions for installing and using the android CLI. The android command-line tool is a critical tool for Android development and helps you create new Android projects, install APKs onto devices and emulators and launch and run apps on them, manage and interact with Android virtual devices (including screenshots and UI inspection), manage Android SDK components, look up official Android documentation, and discover and install official Android skills.
testing-setup
android/skills
Analyze and create a testing strategy for Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end tests.
adaptive
android/skills
Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto, and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API, and how to preserve UI, navigation, scroll, and media playback state across configuration changes (such as folding/unfolding a foldable, rotating a device, or resizing a window). It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as buttons) with varying target sizes, and adaptive layouts (including navigation areas - nav rails and nav bars) using the Compose Grid and FlexBox APIs. It also covers desktop experiences with keyboard shortcuts, tooltips and custom cursors.
Popular mobile skills
design-mobile-apps
designed-by-ai/skills
Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.
ios-design
uizze.sh
Design and review iOS UI/UX for iPhone apps in SwiftUI, UIKit, or React Native. Use for mobile app design, screen redesigns, navigation flows, typography, forms, keyboard and safe-area layout, and accessibility checks. Apply Apple Human Interface Guidelines and consult real product references through the optional Uizze connection.
vercel-react-native-skills
vercel-labs/agent-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
animate-expo
emilkowalski/skills
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.
xcode-project-setup
firebase/agent-skills
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
firebase-remote-config-basics
firebase/agent-skills
Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.