Install the "android-native-dev" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/minimax-ai/android-native-dev into .claude/skills/android-native-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-native-dev", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add aiskillstore/marketplace --skill android-native-dev -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "android-native-dev" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/minimax-ai/android-native-dev into .agents/skills/android-native-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-native-dev", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add aiskillstore/marketplace --skill android-native-dev -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "android-native-dev" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/minimax-ai/android-native-dev into .cursor/skills/android-native-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-native-dev", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add aiskillstore/marketplace --skill android-native-dev -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "android-native-dev" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/minimax-ai/android-native-dev into .gemini/skills/android-native-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-native-dev", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add aiskillstore/marketplace --skill android-native-dev -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "android-native-dev" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/minimax-ai/android-native-dev into .github/skills/android-native-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-native-dev", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add aiskillstore/marketplace --skill android-native-dev -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "android-native-dev" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/minimax-ai/android-native-dev into .opencode/skills/android-native-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-native-dev", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
android-native-dev
GitHub stars
430
Used in
1 other repo
Token cost
~7.1k tokens
SKILL.md length
1,366 words
Files
11 (incl. references)
Skills in repo
1,108
Repo updated
First seen
Licence
MIT
At a glance
Android native application development and UI design guide. An agent skill from aiskillstore/marketplace.
Works in 8 steps: Project Scenario Assessment → Project Configuration → Kotlin Development Standards → …
Tasks that involve Android development
SKILL.md covers 1. Project Scenario Assessment, 2. Project Configuration, 3. Kotlin Development Standards and 4. Jetpack Compose Standards, plus 3 more sections
Calls adb and gradle
What it does
Android Native Dev is an agent skill from aiskillstore/marketplace. Android native application development and UI design guide. Covers Material Design 3, Kotlin/Compose development, project configuration, accessibility, and build troubleshooting. Read this before Android native application development.
Its SKILL.md is about 7.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/accessibility.md`, `references/adaptive-screens.md` and `references/design-style-guide.md`).
It sits in Frontend & Design, covering Android development and UI design. It works with Android, Kotlin, Gradle and MiniMax. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified. The licence is MIT.
When your agent uses it
Tasks that involve Android development
Tasks that involve UI design
Example prompts
“/android-native-dev”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ad8daf7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
adb
gradle
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Android Native Dev loads about 7.1k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 1,366 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~64
When it runs· the whole SKILL.md, loaded when a task matches
~7.1k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~25k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/android-native-dev/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
android-native-dev
description
Android native application development and UI design guide. Covers Material Design 3, Kotlin/Compose development, project configuration, accessibility, and build troubleshooting. Read this before Android native application development.
license
MIT
metadata.version
1.0.0
metadata.category
mobile
metadata.sources
Material Design 3 Guidelines (material.io), Android Developer Documentation (developer.android.com), Google Play Quality Guidelines, WCAG Accessibility…
1. Project Scenario Assessment
Before starting development, assess the current project state:
Scenario
Characteristics
Approach
Empty Directory
No files present
Full initialization required, including Gradle Wrapper
Has Gradle Wrapper
gradlew and gradle/wrapper/ exist
Use ./gradlew directly for builds
Android Studio Project
Complete project structure, may lack wrapper
Check wrapper, run gradle wrapper if needed
Incomplete Project
Partial files present
Check missing files, complete configuration
Key Principles:
Before writing business logic, ensure ./gradlew assembleDebug succeeds
If gradle.properties is missing, create it first and configure AndroidX
# List all available build variants
./gradlew tasks --group="build"
# Build specific variant (flavor + buildType)
./gradlew assembleDevDebug # Dev flavor, Debug build
./gradlew assembleStagingDebug # Staging flavor, Debug build
./gradlew assembleProdRelease # Prod flavor, Release build
# Build all variants of a specific flavor
./gradlew assembleDev # All Dev variants (debug + release)
./gradlew assembleProd # All Prod variants
# Build all variants of a specific build type
./gradlew assembleDebug # All flavors, Debug build
./gradlew assembleRelease # All flavors, Release build
# Install specific variant to device
./gradlew installDevDebug
./gradlew installProdRelease
# Build and install in one command
./gradlew installDevDebug && adb shell am start -n com.example.myapp.dev/.MainActivity
Access BuildConfig in Code:
Note: Starting from AGP 8.0, BuildConfig is no longer generated by default. You must explicitly enable it in your build.gradle.kts:
kotlin
android {
buildFeatures {
buildConfig = true
}
}
kotlin
// Use build config values in your code
val apiUrl = BuildConfig.API_BASE_URL
val isLoggingEnabled = BuildConfig.ENABLE_LOGGING
if (BuildConfig.DEBUG) {
// Debug-only code
}
Flavor-Specific Source Sets:
app/src/
├── main/ # Shared code for all flavors
├── dev/ # Dev-only code and resources
│ ├── java/
│ └── res/
├── staging/ # Staging-only code and resources
├── prod/ # Prod-only code and resources
├── debug/ # Debug build type code
└── release/ # Release build type code
// ❌ Avoid: Non-null assertion !! (may crash)
val name = user!!.name
// ✅ Recommended: Safe call + default value
val name = user?.name ?: "Unknown"
// ✅ Recommended: let handling
user?.let { processUser(it) }
Exception Handling:
kotlin
// ❌ Avoid: Random try-catch in business layer swallowing exceptions
fun loadData() {
try {
val data = api.fetch()
} catch (e: Exception) {
// Swallowing exception, hard to debug
}
}
// ✅ Recommended: Let exceptions propagate, handle at appropriate layer
suspend fun loadData(): Result<Data> {
return try {
Result.success(api.fetch())
} catch (e: Exception) {
Result.failure(e) // Wrap and return, let caller decide handling
}
}
// ✅ Recommended: Unified handling in ViewModel
viewModelScope.launch {
runCatching { repository.loadData() }
.onSuccess { _uiState.value = UiState.Success(it) }
.onFailure { _uiState.value = UiState.Error(it.message) }
}
3.3 Threading & Coroutines (Critical)
Thread Selection Principles:
Operation Type
Thread
Description
UI Updates
Dispatchers.Main
Update View, State, LiveData
Network Requests
Dispatchers.IO
HTTP calls, API requests
File I/O
Dispatchers.IO
Local storage, database operations
Compute Intensive
Dispatchers.Default
JSON parsing, sorting, encryption
Correct Usage:
kotlin
// In ViewModel
viewModelScope.launch {
// Default Main thread, can update UI State
_uiState.value = UiState.Loading
// Switch to IO thread for network request
val result = withContext(Dispatchers.IO) {
repository.fetchData()
}
// Automatically returns to Main thread, update UI
_uiState.value = UiState.Success(result)
}
// In Repository (suspend functions should be main-safe)
suspend fun fetchData(): Data = withContext(Dispatchers.IO) {
api.getData()
}
Common Mistakes:
kotlin
// ❌ Wrong: Updating UI on IO thread
viewModelScope.launch(Dispatchers.IO) {
val data = api.fetch()
_uiState.value = data // Crash or warning!
}
// ❌ Wrong: Executing time-consuming operation on Main thread
viewModelScope.launch {
val data = api.fetch() // Blocking main thread! ANR
}
// ✅ Correct: Fetch on IO, update on Main
viewModelScope.launch {
val data = withContext(Dispatchers.IO) { api.fetch() }
_uiState.value = data
}
3.4 Visibility Rules
kotlin
// Default is public, declare explicitly when needed
class UserRepository { // public
private val cache = mutableMapOf<String, User>() // Visible only within class
internal fun clearCache() {} // Visible only within module
}
// data class properties are public by default, be careful when used across modules
data class User(
val id: String, // public
val name: String
)
3.5 Common Syntax Pitfalls
kotlin
// ❌ Wrong: Accessing uninitialized lateinit
class MyViewModel : ViewModel() {
lateinit var data: String
fun process() = data.length // May crash
}
// ✅ Correct: Use nullable or default value
class MyViewModel : ViewModel() {
var data: String? = null
fun process() = data?.length ?: 0
}
// ❌ Wrong: Using return in lambda
list.forEach { item ->
if (item.isEmpty()) return // Returns from outer function!
}
// ✅ Correct: Use return@forEach
list.forEach { item ->
if (item.isEmpty()) return@forEach
}
3.6 Server Response Data Class Fields Must Be Nullable
kotlin
// ❌ Wrong: Fields declared as non-null (server may not return them)
data class UserResponse(
val id: String = "",
val name: String = "",
val avatar: String = ""
)
// ✅ Correct: All fields declared as nullable
data class UserResponse(
@SerializedName("id")
val id: String? = null,
@SerializedName("name")
val name: String? = null,
@SerializedName("avatar")
val avatar: String? = null
)
3.7 Lifecycle Resource Management
kotlin
// ❌ Wrong: Only adding Observer, not removing
class MyView : View {
override fun onAttachedToWindow() {
super.onAttachedToWindow()
activity?.lifecycle?.addObserver(this)
}
// Memory leak!
}
// ✅ Correct: Paired add and remove
class MyView : View {
override fun onAttachedToWindow() {
super.onAttachedToWindow()
activity?.lifecycle?.addObserver(this)
}
override fun onDetachedFromWindow() {
activity?.lifecycle?.removeObserver(this)
super.onDetachedFromWindow()
}
}
3.8 Logging Level Usage
kotlin
import android.util.Log
// Info: Key checkpoints in normal flow
Log.i(TAG, "loadData: started, userId = $userId")
// Warning: Abnormal but recoverable situations
Log.w(TAG, "loadData: cache miss, fallback to network")
// Error: Failure/error situations
Log.e(TAG, "loadData failed: ${error.message}")
// ❌ Wrong: Calling Composable from non-Composable function
fun showError(message: String) {
Text(message) // Compile error!
}
// ✅ Correct: Mark as @Composable
@Composable
fun ErrorMessage(message: String) {
Text(message)
}
// ❌ Wrong: Using suspend outside LaunchedEffect
@Composable
fun MyScreen() {
val data = fetchData() // Error!
}
// ✅ Correct: Use LaunchedEffect
@Composable
fun MyScreen() {
var data by remember { mutableStateOf<Data?>(null) }
LaunchedEffect(Unit) {
data = fetchData()
}
}
4.2 State Management
kotlin
// Basic State
var count by remember { mutableStateOf(0) }
// Derived State (avoid redundant computation)
val isEven by remember { derivedStateOf { count % 2 == 0 } }
// Persist across recomposition (e.g., scroll position)
val scrollState = rememberScrollState()
// State in ViewModel
class MyViewModel : ViewModel() {
private val _uiState = MutableStateFlow(UiState())
val uiState: StateFlow<UiState> = _uiState.asStateFlow()
}
4.3 Common Compose Mistakes
kotlin
// ❌ Wrong: Creating objects in Composable (created on every recomposition)
@Composable
fun MyScreen() {
val viewModel = MyViewModel() // Wrong!
}
// ✅ Correct: Use viewModel() or remember
@Composable
fun MyScreen(viewModel: MyViewModel = viewModel()) {
// ...
}
Variable names, resource IDs, colors, icons, and XML elements must not use Android reserved words or system resource names. Using reserved names causes build errors or resource conflicts.
Common Reserved Names to Avoid:
Category
Reserved Names (Do NOT Use)
Colors
background, foreground, transparent, white, black
Icons/Drawables
icon, logo, image, drawable
Views
view, text, button, layout, container
Attributes
id, name, type, style, theme, color
System
app, android, content, data, action
Examples:
xml
<!-- ❌ Wrong: Using reserved names -->
<color name="background">#FFFFFF</color>
<color name="icon">#000000</color>
<!-- ✅ Correct: Add prefix or specific naming -->
<color name="app_background">#FFFFFF</color>
<color name="icon_primary">#000000</color>
kotlin
// ❌ Wrong: Variable names conflict with system
val icon = R.drawable.my_icon
val background = Color.White
// ✅ Correct: Use descriptive names
val appIcon = R.drawable.my_icon
val screenBackground = Color.White
Note: Only add test dependencies when the user explicitly asks for testing.
A well-tested Android app uses layered testing: fast local unit tests for logic, instrumentation tests for UI and integration, and Gradle Managed Devices to run emulators reproducibly on any machine — including CI.
8.1 Test Dependencies
Before adding test dependencies, inspect the project's existing versions to avoid conflicts:
Check gradle/libs.versions.toml — if present, add test deps using the project's version catalog style
Check existing build.gradle.kts for already-pinned dependency versions
Match version families using the table below
Version Alignment Rules:
Test Dependency
Must Align With
How to Check
kotlinx-coroutines-test
Project's kotlinx-coroutines-core version
Search for kotlinx-coroutines in build files or version catalog
compose-ui-test-junit4
Project's Compose BOM or compose-compiler
Search for compose-bom or compose.compiler in build files
espresso-*
All Espresso artifacts must use the same version
Search for espresso in build files
androidx.test:runner, rules, ext:junit
Should use compatible AndroidX Test versions
Search for androidx.test in build files
mockk
Must support the project's Kotlin version
Check kotlin version in root build.gradle.kts or version catalog
Dependencies Reference — add only the groups you need:
kotlin
dependencies {
// --- Local unit tests (src/test/) ---
testImplementation("junit:junit:<version>") // 4.13.2+
testImplementation("org.robolectric:robolectric:<version>") // 4.16.1+
testImplementation("io.mockk:mockk:<version>") // match Kotlin version
testImplementation("org.jetbrains.kotlinx:kotlinx-coroutines-test:<version>") // match coroutines-core
testImplementation("androidx.arch.core:core-testing:<version>") // InstantTaskExecutorRule for LiveData
testImplementation("app.cash.turbine:turbine:<version>") // Flow/StateFlow testing
// --- Instrumentation tests (src/androidTest/) ---
androidTestImplementation("androidx.test.ext:junit:<version>")
androidTestImplementation("androidx.test:runner:<version>")
androidTestImplementation("androidx.test:rules:<version>")
androidTestImplementation("androidx.test.espresso:espresso-core:<version>")
androidTestImplementation("androidx.test.espresso:espresso-contrib:<version>") // RecyclerView, Drawer
androidTestImplementation("androidx.test.espresso:espresso-intents:<version>") // Intent verification
androidTestImplementation("androidx.test.espresso:espresso-idling-resource:<version>")
androidTestImplementation("androidx.test.uiautomator:uiautomator:<version>")
// --- Compose UI tests (only if project uses Compose) ---
androidTestImplementation("androidx.compose.ui:ui-test-junit4") // version from Compose BOM
debugImplementation("androidx.compose.ui:ui-test-manifest") // required for createComposeRule
}
Note: If the project uses a Compose BOM, ui-test-junit4 and ui-test-manifest don't need explicit versions — the BOM manages them.
Enable Robolectric resource support in the android block:
See Testing for detailed examples, code patterns, and Gradle Managed Device configuration.
8.3 Testing Commands
bash
# Local unit tests (fast, no emulator)
./gradlew test # all modules
./gradlew :app:testDebugUnitTest # app module, debug variant
# Single test class
./gradlew :app:testDebugUnitTest --tests "com.example.myapp.CounterViewModelTest"
# Instrumentation tests (requires device or managed device)
./gradlew connectedDebugAndroidTest # on connected device
./gradlew pixel6Api34DebugAndroidTest # on managed device
# Both together
./gradlew test connectedDebugAndroidTest
# Test with coverage report (JaCoCo)
./gradlew testDebugUnitTest jacocoTestReport
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in aiskillstore/marketplace, which our catalogue first saw on October 7, 2026.
Android Native Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Android Native Dev compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Android Native Dev this skillaiskillstore/marketplace
Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.
Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.
Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y…
Android native application development and UI design guide. An agent skill from aiskillstore/marketplace. Android Native Dev is an agent skill from aiskillstore/marketplace. Android native application development and UI design guide.
When should I use Android Native Dev?
Android Native Dev fits situations like: tasks that involve Android development; tasks that involve UI design.
How do I install Android Native Dev in Claude Code?
Run `npx skills add aiskillstore/marketplace --skill android-native-dev -a claude-code`. Or copy the skill folder (skills/minimax-ai/android-native-dev in aiskillstore/marketplace) into .claude/skills/android-native-dev in your project. Claude Code loads it when a task matches its description.
How do I install Android Native Dev in Codex?
Run `npx skills add aiskillstore/marketplace --skill android-native-dev -a codex`. Or copy the skill folder (skills/minimax-ai/android-native-dev in aiskillstore/marketplace) into .agents/skills/android-native-dev in your project. Codex loads it when a task matches its description.
Can I use Android Native Dev in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiskillstore/marketplace --skill android-native-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/android-native-dev, .gemini/skills/android-native-dev, .github/skills/android-native-dev and .opencode/skills/android-native-dev in your project.
What does Android Native Dev need to run?
Going by SKILL.md and its folder, Android Native Dev needs the command-line tools its instructions call (adb and gradle).
Does Android Native Dev access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Android Native Dev safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Android Native Dev use?
Android Native Dev is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Android Native Dev use?
About 7.1k tokens (SKILL.md is roughly 28k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.
What are the alternatives to Android Native Dev?
Skills that share tags, products or a category with Android Native Dev: Hz Metavrx UI Set (meta-quest/agentic-tools, 213 stars), Android Development (dpconde/claude-android-skill, 336 stars), Claude Android Ninja (Drjacky/claude-android-ninja, 124 stars) and Expo Brownfield Integration (mweinbach/agent-coworker, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Android Native Dev?
aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,108 skills in this directory. The repository was last updated on October 7, 2026.
Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.