Android Kotlin Development

What this skill does

• •Scaffolds MVVM-based Android architecture
• •Generates type-safe API service definitions
• •Provides templates for Jetpack Compose UI components
• •Implements reactive data flows with StateFlow
• •Configures local data persistence using Room

When to use it

• ✓Starting a new native Android project with modern architectural standards
• ✓Implementing data-driven screens using Jetpack Compose
• ✓Setting up modular network layers with Retrofit
• ✓Enforcing consistent MVVM patterns within a team codebase

When not to use it

• ✕Cross-platform development requiring frameworks like React Native or Flutter
• ✕Legacy Android projects that strictly forbid Kotlin and Jetpack libraries

How to invoke it

Example prompts that trigger this skill:

• “Generate a new ViewModel for my User profile feature.”
• “Create a Retrofit service interface for handling authentication endpoints.”
• “Write a Jetpack Compose screen for the dashboard view.”
• “Implement a Room database entity for local caching.”
• “Refactor this fragment to follow the current MVVM architectural pattern.”

Example workflow

1. Define your data models as Kotlin data classes.
2. Invoke the skill to generate a corresponding Retrofit API interface.
3. Create a ViewModel to handle business logic and state management.
4. Build the UI using the generated Jetpack Compose templates.
5. Apply Hilt annotations for dependency injection across the feature.

Prerequisites

• –Android Studio installed
• –Kotlin SDK
• –Gradle build environment

Pitfalls & limitations

• !Risk of over-engineering simple UI components using complex MVVM patterns
• !Potential performance issues if StateFlow observers are not cleared correctly
• !Hard-coding sensitive API tokens instead of using secure storage

FAQ

How it compares

Unlike a generic LLM prompt, this skill embeds validated quality gates and architectural templates, ensuring code consistency that manual prompting often misses.

Source & trust

From the source: “# Android Kotlin Development ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Build robust native Android applications using Kotlin with modern architecture…”

# Android Kotlin Development

## Table of Contents

- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)

## Overview

Build robust native Android applications using Kotlin with modern architecture patterns, Jetpack libraries, and Compose for declarative UI.

## When to Use

- Creating native Android applications with best practices
- Using Kotlin for type-safe development
- Implementing MVVM architecture with Jetpack
- Building modern UIs with Jetpack Compose
- Integrating with Android platform APIs

## Quick Start

Minimal working example:

```kotlin
// Models
data class User(
  val id: String,
  val name: String,
  val email: String,
  val avatarUrl: String? = null
)

data class Item(
  val id: String,
  val title: String,
  val description: String,
  val imageUrl: String? = null,
  val price: Double
)

// API Service with Retrofit
interface ApiService {
  @GET("/users/{id}")
  suspend fun getUser(@Path("id") userId: String): User

  @PUT("/users/{id}")
  suspend fun updateUser(
    @Path("id") userId: String,
    @Body user: User
// ... (see reference guides for full implementation)
```

## Reference Guides

Detailed implementations in the `references/` directory:

| Guide | Contents |
|---|---|
| [Models & API Service](references/models-api-service.md) | Models & API Service |
| [MVVM ViewModels with Jetpack](references/mvvm-viewmodels-with-jetpack.md) | MVVM ViewModels with Jetpack |
| [Jetpack Compose UI](references/jetpack-compose-ui.md) | Jetpack Compose UI |

## Best Practices

### ✅ DO

- Use Kotlin for all new Android code
- Implement MVVM with Jetpack libraries
- Use Jetpack Compose for UI development
- Leverage coroutines for async operations
- Use Room for local data persistence
- Implement proper error handling
- Use Hilt for dependency injection
- Use StateFlow for reactive state
- Test on multiple device types
- Follow Android design guidelines

### ❌ DON'T

- Store tokens in SharedPreferences
- Make network calls on main thread
- Ignore lifecycle management
- Skip null safety checks
- Hardcode strings and resources
- Ignore configuration changes
- Store passwords in code
- Deploy without device testing
- Use deprecated APIs
- Accumulate memory leaks

Quoted from aj-geddes/useful-ai-prompts for reference — see the original for the authoritative, latest version.

Recommended Rules

Recommended Workflows

Recommended MCP Servers