Skills Plugins MCP Prompt Model 博客 我的中心
Data & Consulting #data #database

android-development

Create production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices. Use when building Android apps with Kotlin, Jetpack Compose, MVVM architecture, Hilt dependency injection, Room database, or multi-module projects. Triggers on requests to create Android projects, screens, ViewModels, repositories, feature modules, or when asked about Android architecture patterns.

DeepseekModel Curated skill Quality Excellent · 78 v1.0.0

Get

https://deepseekmodel.com/api/download.php?id=dpconde-claude-android-skill-skill-md&format=skill
Download .skill Standard format with system_prompt and model_config, ready for any agent framework
The actual content of the system_prompt field in the .skill file.
name android-development description Create production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices. Use when building Android apps with Kotlin, Jetpack Compose, MVVM architecture, Hilt dependency injection, Room database, or multi-module projects. Triggers on requests to create Android projects, screens, ViewModels, repositories, feature modules, or when asked about Android architecture patterns. Android Development Build Android applications following Google's official architecture guidance, as demonstrated in the NowInAndroid reference app. Quick Reference Task Reference File Project structure & modules modularization.md Architecture layers (UI, Domain, Data) architecture.md Jetpack Compose patterns compose-patterns.md Gradle & build configuration gradle-setup.md Testing approach testing.md Workflow Decision Tree Creating a new project? → Read modularization.md for project structure → Use templates in assets/templates/ Adding a new feature? → Create feature module with api and impl submodules → Follow patterns in architecture.md Building UI screens? → Read compose-patterns.md → Create Screen + ViewModel + UiState Setting up data layer? → Read data layer section in architecture.md → Create Repository + DataSource + DAO Core Principles Offline-first : Local database is source of truth, sync with remote Unidirectional data flow : Events flow down, data flows up Reactive streams : Use Kotlin Flow for all data exposure Modular by feature : Each feature is self-contained with clear boundaries Testable by design : Use interfaces and test doubles, no mocking libraries Architecture Layers ┌─────────────────────────────────────────┐ │ UI Layer │ │ (Compose Screens + ViewModels) │ ├─────────────────────────────────────────┤ │ Domain Layer │ │ (Use Cases - optional, for reuse) │ ├─────────────────────────────────────────┤ │ Data Layer │ │ (Repositories + DataSources) │ └─────────────────────────────────────────┘ Module Types app/ # App module - navigation, scaffolding feature/ ├── featurename/ │ ├── api/ # Navigation keys (public) │ └── impl/ # Screen, ViewModel, DI (internal) core/ ├── data/ # Repositories ├── database/ # Room DAOs, entities ├── network/ # Retrofit, API models ├── model/ # Domain models (pure Kotlin) ├── common/ # Shared utilities ├── ui/ # Reusable Compose components ├── designsystem/ # Theme, icons, base components ├── datastore/ # Preferences storage └── testing/ # Test utilities Creating a New Feature Create feature:myfeature:api module with navigation key Create feature:myfeature:impl module with: MyFeatureScreen.kt - Composable UI MyFeatureViewModel.kt - State holder MyFeatureUiState.kt - Sealed interface for states MyFeatureNavigation.kt - Navigation setup MyFeatureModule.kt - Hilt DI module Standard File Patterns ViewModel Pattern @HiltViewModel class MyFeatureViewModel @Inject constructor ( private val myRepository: MyRepository, ) : ViewModel() { val uiState: StateFlow<MyFeatureUiState> = myRepository .getData() .map { data -> MyFeatureUiState.Success( data ) } .stateIn( scope = viewModelScope, started = SharingStarted.WhileSubscribed( 5_000 ), initialValue = MyFeatureUiState.Loading, ) fun onAction (action: MyFeatureAction ) { when (action) { is MyFeatureAction.ItemClicked -> handleItemClick(action.id) } } } UiState Pattern sealed interface MyFeatureUiState { data object Loading : MyFeatureUiState data class Success ( val items: List<Item>) : MyFeatureUiState data class Error ( val message: String) : MyFeatureUiState } Screen Pattern @Composable internal fun MyFeatureRoute ( onNavigateToDetail: ( String ) -> Unit , viewModel: MyFeatureViewModel = hiltViewModel() , ) { val uiState by viewModel.uiState.collectAsStateWithLifecycle() MyFeatureScreen( uiState = uiState, onAction = viewModel::onAction, onNavigateToDetail = onNavigateToDetail, ) } @Composable internal fun MyFeatureScreen ( uiState: MyFeatureUiState , onAction: ( MyFeatureAction ) -> Unit , onNavigateToDetail: ( String ) -> Unit , ) { when (uiState) { is MyFeatureUiState.Loading -> LoadingIndicator() is MyFeatureUiState.Success -> ContentList(uiState.items, onAction) is MyFeatureUiState.Error -> ErrorMessage(uiState.message) } } Repository Pattern interface MyRepository { fun getData () : Flow<List<MyModel>> suspend fun updateItem (id: String , data : MyModel ) } internal class OfflineFirstMyRepository @Inject constructor ( private val localDataSource: MyDao, private val networkDataSource: MyNetworkApi, ) : MyRepository { override fun getData () : Flow<List<MyModel>> = localDataSource.getAll().map { entities -> entities.map { it.toModel() } } override suspend fun updateItem (id: String , data : MyModel ) { localDataSource.upsert( data .toEntity()) } } Key Dependencies // Gradle version catalog (libs.versions.toml) [versions] kotlin = "1.9.x" compose-bom = "2024.x.x" hilt = "2.48" room = "2.6.x" coroutines = "1.7.x" [libraries] androidx-compose-bom = { group = "androidx.compose" , name = "compose-bom" , version.ref = "compose-bom" } hilt-android = { group = "com.google.dagger" , name = "hilt-android" , version.ref = "hilt" } room-runtime = { group = "androidx.room" , name = "room-runtime" , version.ref = "room" } Build Configuration Use convention plugins in build-logic/ for consistent configuration: AndroidApplicationConventionPlugin - App modules AndroidLibraryConventionPlugin - Library modules AndroidFeatureConventionPlugin - Feature modules AndroidComposeConventionPlugin - Compose setup AndroidHiltConventionPlugin - Hilt setup See gradle-setup.md for complete build configuration.
Keywords that activate this skill. Click one to copy it.

This skill does not provide trigger words.

The downloaded .skill package contains the following fields.
Field Description
formatFormat tag (skill/v1)
skill_idUnique skill ID
nameSkill name
versionVersion
descriptionDescription
categoryCategories (array)
trigger_wordsTrigger words
tagsTags
sourceSource
source_urlSource URL (this page)
exported_atExported at (set per download)
system_promptSystem prompt body
model_configModel config: provider / model / temperature / max_tokens / top_p
examplesExamples
install_guideImport guide for Coze / Dify / Claude / custom frameworks
The same skill can be exported in different platform formats.
.skill Standard format with system_prompt and model_config, ready for any agent framework Download
.skillpro Enhanced format with scripts, tools, dependencies and hooks Download
.json Plain JSON export with system_prompt and model parameters only Download
Coze Markdown with frontmatter, for Coze platform import Download
Dify Dify DSL, import directly after creating an app Download

每日精选 Skill 推荐,免费送到你邮箱

输入邮箱,每天接收一个精选 AI Agent 技能推荐。完全免费,持续更新。

验证码 --

提交后我们会发送一封确认邮件,点击邮件里的链接才会开始收信。

完全免费,取消任意时间。我们不会发送垃圾邮件。