TajsOS

Overview of Google's recommended Android app architecture: three-layer model (UI, Domain, Data), core principles (SoC, adaptive layouts, SSOT, UDF, main-safety), dependency injection with Hilt, general best practices, and multi-module structure. Use this skill for general architecture questions. For layer-specific code review, use the focused layer skills: ui-layer, data-layer, domain-layer.

Jetpack Compose and Compose Multiplatform (KMP/CMP) architecture skill. Only use when the user explicitly mentions "compose-skill", "@compose-skill", or "use compose skill" in their message. Do NOT auto-activate based on keyword matching — this skill should only be triggered by direct user request.

Google's recommended Data Layer architecture for Android. Use this skill when designing, implementing, or reviewing repositories, data sources, data models, model-per-layer separation, naming conventions, threading, error propagation, lifecycle/scoping, or testing in the data layer. Based on developer.android.com/topic/architecture/data-layer and the official Android architecture recommendations page.

Google's recommended Domain Layer architecture for Android. Use this skill when deciding whether to add a domain layer, designing use cases, reviewing use case implementations, or checking that business logic is correctly placed between the UI and data layers. Based on developer.android.com/topic/architecture/domain-layer and the official Android architecture recommendations page.

Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.

Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android project. It solves the problem of converting the UI of a legacy XML View into modern, declarative Compose components while maintaining interoperability.

Learn how to install and migrate to Jetpack Navigation 3, and how to implement features and patterns such as deep links, multiple backstacks, scenes (dialogs, bottom sheets, list-detail, two-pane, supporting pane), conditional navigation (such as logged-in navigation vs anonymous), returning results from flows, integration with Hilt, ViewModel, Kotlin, and view interoperability.

Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use when developers want to optimize their app's size, remove redundant or overly broad keep rules, or troubleshoot Proguard configurations.

TajsOS Compose screen-system overlay. Use for shell/screen/content ownership boundaries and consistent screen structure decisions.

TajsOS build overlay for Kotlin Multiplatform + Compose Multiplatform projects, including version alignment and repo-valid verification commands.

TajsOS KMP architecture overlay. Use for commonMain vs platform boundaries, shared state placement, and platform abstraction decisions.

TajsOS product and UX overlay guidance. Use for product framing, naming, feature prioritization, and coherence-focused UX decisions.

TajsOS repo quality overlay. Use for pragmatic CI/test/lint/coverage improvements aligned with current repository reality.

Google's recommended UI layer architecture for Android. Use this skill when designing, implementing, or reviewing ViewModels, UI state, Compose screens, state collection, state production, lifecycle effects, UI events, navigation, or any UI-layer code. Based on developer.android.com/topic/architecture/ui-layer, the events, stateholders, and state-production sub-pages, and the official Android architecture recommendations page.