메뉴
Review Android or Kotlin Multiplatform projects for UI, domain, and data layer consistency. Use when checking feature structure, layer boundaries, model ownership, mappers, use cases, repositories, TODO/FIXME comments, Compose UI flows, performance bottlenecks, or platform-specific separation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | android-layered-architecture-review |
| description | Review Android or Kotlin Multiplatform projects for UI, domain, and data layer consistency. Use when checking feature structure, layer boundaries, model ownership, mappers, use cases, repositories, TODO/FIXME comments, Compose UI flows, performance bottlenecks, or platform-specific separation. |
Use this skill when reviewing Android code that follows a UI -> Domain -> Data architecture.
The goal is not to redesign features.
The goal is to keep the project consistent, predictable, testable, and safe to maintain over time.
Prefer small, mechanical, behavior-preserving improvements.
Do not rewrite entire features unless the user explicitly asks for that.
Before making architectural decisions, read:
references/android-layer-rules.md
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.
Helps developers integrate, debug, and resolve Play Engage SDK implementation issues. Use when adding Engage SDK support, generating publishing code, mapping data classes to entities, or fixing SDK-related errors.
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.
Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API. It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as buttons) with varying target sizes, and adaptive layouts (including navigation areas - nav rails and nav bars) using the Compose Grid and FlexBox APIs.
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.
Use this skill to integrate the Jetpack Compose Styles API into an Android project. This skill guides you through upgrading dependencies, setting up component themes, making custom components styleable, and migrating existing layout properties to use unified styles. Migrate custom design system components, replace hard coded parameters with Style attributes, and use Modifier.styleable for interaction states.