kez-lab

Verify and bootstrap the Google Android CLI (`android` command) on the user's machine. Use when the `android` command is missing, outdated, misconfigured (wrong SDK path), or when the user wants to set up `.androidrc` or wire the CLI into agents (`android init`). Triggers include "android cli 설치", "android command not found", "android update", "sdk 경로", ".androidrc", "android init", "android cli 환경설정". Do NOT use this skill for day-to-day deploy/emulator/screen workflows — those have dedicated skills.

Build and deploy an Android app to a connected device or emulator using Gradle + the Android CLI's `android describe` and `android run`. Use whenever the user wants to install / launch / sideload an app, test a code change on a device, deploy a service component, or push split APKs. Triggers include "앱 띄워줘", "디바이스에 설치", "에뮬에 deploy", "APK 설치", "run on device", "앱 빌드해서 띄워줘", "deploy". Do NOT use this skill to create or start emulators — use `android-emulator` for that.

Look up official Android best practices, guidance, and recommended patterns via the Android Knowledge Base (`android docs search` + `android docs fetch kb://…`). Use this **before** WebSearch when the question is about Android-platform topics (Compose, performance, accessibility, lifecycle, intents, build, security, edge-to-edge, foreground services, etc.). Triggers include "안드로이드 베스트 프랙티스", "Android best practice", "Compose performance", "edge-to-edge", "android docs", "공식 가이드", "권장 패턴". Do NOT use this skill for third-party libraries (Retrofit, OkHttp, Hilt) — use Context7 MCP for those.

Manage Android Virtual Devices and required system images via the Android CLI (`android emulator` + `android sdk install`). Use when the user wants to create, list, start, or stop an emulator; install a system image needed for an emulator; or recover from "no devices connected". Triggers include "에뮬레이터 만들어줘", "에뮬 켜줘", "AVD 생성", "system image 설치", "에뮬 종료", "에뮬레이터 목록", "Pixel 에뮬". Do NOT use this skill to deploy apps — `android-deploy` handles that.

Create a new Android project from an official Android CLI template using `android create`. Use when the user wants to start a new Android app from scratch, scaffold a sample project, or compare templates with `--dry-run`. Triggers include "새 안드로이드 프로젝트", "안드로이드 프로젝트 만들어줘", "compose 템플릿", "android create", "프로젝트 생성", "scaffold". Do NOT use this skill to add modules to an existing project — use Gradle / Studio for module creation.

Capture annotated screenshots of a running Android app and translate UI element labels into actual tap coordinates, using `android screen capture` + `android screen resolve` and the structured `android layout` JSON. Use when the user wants to take a screenshot, automate UI interactions without hardcoding pixel coordinates, compare UI state before/after a change, or extract the view hierarchy. Triggers include "스크린샷", "screenshot", "버튼 클릭 자동화", "UI 자동화", "tap", "view hierarchy", "layout 비교", "이 버튼 좌표". Do NOT use this skill for visual regression testing of release builds — use Playwright/Espresso for that.

Write git commit messages following the project's chosen convention (Conventional Commits, Korean variant, Gitmoji, or custom). Reads style from `.claude/android-skills.json` and onboards the project once if the config is missing. Use when the user asks to commit, draft a commit message, fix up a commit, or after staging changes. Triggers include "commit message", "커밋 메시지", "커밋 메세지", "git commit", "커밋해줘", "커밋 작성".

Generate Jetpack Compose `@Preview` functions and `PreviewParameterProvider` classes. Use whenever the user wants to add previews to a `@Composable`, set up multi-config previews (light/dark, screen sizes, font scale, locale, dynamic color), or needs a `PreviewParameterProvider` for composables that take complex parameters. Triggers include phrases like "프리뷰 추가", "preview 만들어줘", "@Preview", "PreviewParameterProvider", "다크모드 프리뷰", "multi preview".

Use when verifying the Image Calendar Android MVP with official Android CLI, preserving screenshots/layouts/action logs under raw/verification, and updating QA evidence.

Use after product, design, implementation, verification, or decision changes to synchronize raw evidence, LLM Wiki pages, SDD specs, and project logs.

Use when deploying or launching an Android APK on a connected device or emulator with the official android run command, including debug APK verification and install failure diagnosis.

Use when checking, updating, initializing, or configuring the official Android CLI for agent workflows, including android update, android init, android info, command discovery, and .androidrc SDK configuration.

Use when searching official Android Knowledge Base docs through Android CLI or finding/installing official Android skills such as edge-to-edge, navigation, AGP upgrades, R8 analyzer, and Compose migration.

Use when running an Android user journey or smoke test with Android CLI layout, screen capture, screen resolve, and scripted interactions against a connected device.

Use when creating Android projects from official Android CLI templates or describing an existing Android project to find variants, build targets, and APK output artifacts.

Use when listing, installing, updating, or removing Android SDK packages, or creating, listing, starting, and stopping Android emulators with official Android CLI commands.

Run long autonomous improvement loops for the Compose-DateTimePicker repository. Use when the maintainer asks for a Codex goal, 12-hour improvement run, autonomous API/library hardening, branch/PR planning, worktree strategy, or repo-scoped execution plan for this Kotlin Multiplatform picker library.

Audit and improve Compose-DateTimePicker public API ergonomics, API stability, ABI dumps, KDoc, README usage, picker state contracts, item constraints, formatting, semantics, and cross-component invariants. Use when working on Picker, TimePicker, DatePicker, YearMonthPicker, DateRangePicker, or any public API change in this repository.

Select and run fast local verification gates for Compose-DateTimePicker changes while hosted GitHub Actions PR automation is disabled. Use before handoff, PR creation, merging, or after modifying Kotlin source, public APIs, README/CHANGELOG docs, sample app code, or workflow files.

Design, implement, migrate, review, and test complex Android ViewModel flows with Afsm, including State/Phase/Data/Event/Command modeling, the afsmMachine DSL, afsmHost integration, restoration, transition tests, and Mermaid graph generation. Use when adopting Afsm in a Kotlin or Android project, adding or changing an Afsm machine, refactoring branching ViewModel flow into Afsm, diagnosing Afsm behavior, or reviewing an Afsm integration. Do not use for simple screens where ordinary ViewModel plus StateFlow is clearer or for changing Afsm library internals.