From android-dev
Android feature implementation: creating from scratch, extending existing features, or refactoring to match the architectural standard. Automatically determines the working mode based on context. Use for any tasks involving writing/modifying Android code. <example> Context: User wants to create a new screen user: "create an authorization screen with email and password" assistant: "Using implement skill in create mode to build the auth feature." </example> <example> Context: User wants to add functionality to an existing screen user: "add pagination to the catalog screen" assistant: "Using implement skill in modify mode to extend the catalog feature." </example> <example> Context: User wants to bring code up to standard user: "refactor the profile screen to match our architecture" assistant: "Using implement skill in refactor mode to migrate the profile feature." </example> <example> Context: A list of architectural violations was received from review user: "fix the violations from the review" assistant: "Using implement skill to fix architectural violations." </example>
How this skill is triggered — by the user, by Claude, or both
Slash command
/android-dev:implementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You implement Android feature layers strictly following the project's architectural rules.
examples/ExampleData.ktexamples/ExampleDataSource.ktexamples/ExampleDiModuleKodein.ktexamples/ExampleDiModuleKoin.ktexamples/ExampleRepository.ktexamples/ExampleResponse.ktexamples/ExampleScreen.ktexamples/ExampleUseCase.ktexamples/ExampleView.ktexamples/ExampleViewAction.ktexamples/ExampleViewEvent.ktexamples/ExampleViewModel.ktexamples/ExampleViewState.ktexamples/IExampleRepository.ktreferences/architecture.mdreferences/base-viewmodel.mdreferences/migration-guide.mdreferences/modification-rules.mdreferences/theme-system.mdYou implement Android feature layers strictly following the project's architectural rules.
Task from user: $ARGUMENTS
Automatically determine the task type:
Triggers:
Triggers:
Triggers:
Triggers:
[Structure] → packages and files[Screen] → {Feature}Screen.kt[View] → {Feature}View.kt[ViewModel] → {Feature}ViewModel.kt[ViewState/Event/Action] → corresponding files[UseCase] → *UseCase.kt[Repository] → *Repository.kt[DI] → *DiModule.kt / *Module.kt[Rendering] → {Feature}View.kt[Interaction] → {Feature}View.kt + ViewModel[Navigation] → {Feature}Screen.kt + ViewModel[Data] → ViewModel + ViewState[Accessibility] → {Feature}View.kt[Crash] → ViewModel / UseCaseskoin or kodein from build.gradle or existing modules$CLAUDE_PLUGIN_ROOT/rules/android-core.md (required)Read references: $CLAUDE_PLUGIN_ROOT/skills/implement/references/architecture.md, $CLAUDE_PLUGIN_ROOT/skills/implement/references/base-viewmodel.md, $CLAUDE_PLUGIN_ROOT/skills/implement/references/theme-system.md
Use examples/ as a template for each file.
Creation order:
feature/{featureName}/
presentation/screen/
presentation/view/
presentation/viewmodel/
domain/usecase/
domain/repository/
data/datasource/
data/repository/
di/
{Feature}ViewState.kt — data class with default values{Feature}ViewEvent.kt — sealed class of UI events{Feature}ViewAction.kt — sealed class of one-time actions{Feature}ViewModel.kt — extends BaseSharedViewModel{Feature}Screen.kt — thin adapter{Feature}View.kt — pure UI with PreviewI{Feature}Repository.kt — interface{Feature}Repository.kt — implementation{Feature}DiModule.kt — DI moduleRead references: $CLAUDE_PLUGIN_ROOT/skills/implement/references/modification-rules.md
Read references: $CLAUDE_PLUGIN_ROOT/skills/implement/references/migration-guide.md, $CLAUDE_PLUGIN_ROOT/skills/implement/references/architecture.md
remember/LaunchedEffect in Screen — move them to View, do NOT delete them. PagerState, ScrollState, LazyListState and related snapshotFlow belong in View, never in Screen.npx claudepluginhub gorban-dev/gor-dev-plugins --plugin android-devImplements MVVM, Clean Architecture layers, Hilt dependency injection, and repository pattern in Android apps with Kotlin examples.
Guides Android and Kotlin development with Jetpack Compose, architecture patterns, coroutines, Room, navigation, and Hilt. Activate when building Android apps or reviewing Android-specific code.
Guides production-grade Android app development across native (Kotlin/Java), Flutter, and React Native stacks, covering architecture, UI, testing, build, and release.