android-development
Android development guidelines and best practices for the mobile-dev team
What this skill does
# Android Development Guidelines ## Kotlin and Jetpack Compose Fundamentals - Use Kotlin 1.9+ with modern language features - Prefer Jetpack Compose for new UI components - Use Compose state management (@State, @Remember, @ViewModel) - Leverage Kotlin Coroutines for asynchronous operations - Use Kotlin Flow for reactive streams - Follow Kotlin coding conventions ## Android Architecture Patterns - **MVVM**: Use with ViewModel and LiveData/StateFlow - **Clean Architecture**: Separate data, domain, and presentation layers - **Repository Pattern**: Abstract data sources - Implement dependency injection with Hilt - Separate business logic from UI code - Use interfaces for abstraction and testing ## Android Jetpack Libraries - **Room**: Use for local database persistence - **WorkManager**: Use for background tasks - **Navigation Component**: Use for app navigation - **DataStore**: Use for key-value storage - **Paging 3**: Use for paginated data - **CameraX**: Use for camera functionality - **BiometricPrompt**: Use for biometric authentication - **AppCompat**: Use for backward compatibility ## Material Design 3 Guidelines - Follow Material Design 3 principles - Use Material 3 components and theming - Implement proper elevation and shadows - Use Material Icons for consistency - Support different screen sizes and densities - Implement responsive layouts - Support Dark Theme properly - Use motion and animations appropriately ## Android Permissions and Security - Request runtime permissions properly - Use permission best practices - Implement proper certificate pinning - Use Android Keystore for secure storage - Follow security best practices - Implement proper network security configuration - Use ProGuard/R8 for code obfuscation ## Google Play Store Submission - Follow Google Play Developer Policies - Prepare app bundle (AAB) for upload - Prepare screenshots and store listing - Test with Internal and Closed Testing tracks - Handle app updates and versioning properly - Comply with privacy and data collection policies - Use Play Console for distribution and analytics ## Android Performance Optimization - Use Android Profiler for performance analysis - Optimize APK/AAB size with code shrinking - Use leak detection tools (LeakCanary) - Implement proper image loading and caching - Optimize network requests and data transfer - Reduce app startup time - Use efficient layouts and view binding - Optimize battery usage ## Android Testing Frameworks - **JUnit**: Use for unit tests - **Espresso**: Use for UI tests - **Compose Testing**: Use for Compose UI tests - **Robolectric**: Use for local unit tests - **MockK**: Use for mocking in tests - **Truth**: Use for assertion libraries - Write testable code with dependency injection
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.