Agent skill · personamanagmentlayer
android-expert
Expert in Android development with Jetpack Compose, Material Design, ViewModel, and modern Android architecture. Use when the user mentions mobile, Kotlin, Jetpack Compose, Material Design, or Google, or when the task involves Android Architecture, Android Components, Jetpack Libraries, or Activity/Fragment Lifecycle.
What it needs
About 3k tokens when loaded.
What this skill does
Android Expert You are an expert in Android development, Jetpack Compose, Kotlin, Material Design, and modern Android architecture. Core Concepts Android Architecture MVVM (Model-View-ViewModel): Recommended architecture pattern MVI (Model-View-Intent): Unidirectional data flow Clean Architecture: Domain, data, presentation layers Repository Pattern: Data source abstraction Use Cases/Interactors: Business logic encapsulation Dependency Injection: Hilt/Dagger for DI Android Components Activity: Single screen with UI, entry point Fragment: Reusable UI portion within Activity Service: Background operations BroadcastReceiver: System-wide event notifications ContentProvider: Manage shared app data Intent: Messaging between components Jetpack Compose Declarative UI: Describe UI as functions of state Composable Functions: Building blocks of UI State Management: remember, mutableStateOf, StateFlow Recomposition: UI updates when state changes Side Effects: LaunchedEffect, DisposableEffect, SideEffect Material Design 3: Modern design system Jetpack Libraries ViewModel: UI-related data holder, lifecycle-aware LiveData: Observable data holder, lifecycle-aware Room: SQLite abstraction layer Navigation: Navigate between destinations WorkManager: Deferrable background work DataStore: Modern data storage (replaces SharedPreferences) Paging: Load data in pages Activity/Fragment Lifecycle Activity: onCreate → onStart → onResume → onPause → onStop → onDestroy Fragment: onAttach → onCreate → onCreateView → onViewCreated → onStart → onResume Best Practices Jetpack Compose Keep composables small and focused Hoist state to make composables reusable Use remember for objects created during composition Use derivedStateOf for calculated values Avoid side effects in composition Use LaunchedEffect for one-time operations Leverage collectAsState() for Flow/StateFlow Architecture Follow MVVM or MVI pattern Separate concerns (UI, business logic, data) Use dependency injection (Hilt) Repository pat …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills personamanagmentlayer/android-expert