메뉴
Use when adding or changing Compose Screen UI, Preview, feature UI components, dialogs, bottom sheets, loading UI, paging UI, or shared UI placement in this Android repository.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | implementing-ui |
| description | Use when adding or changing Compose Screen UI, Preview, feature UI components, dialogs, bottom sheets, loading UI, paging UI, or shared UI placement in this Android repository. |
feature UI는 <Feature>Screen, preview, feature component를 같은 Screen 파일 흐름에 맞춘다.
feature/<feature-name>/impl/src/main/.../*Screen.ktfeature/<feature-name>/impl/src/main/.../component/*core:designsystem, core:ui, feature 내부 component/component/에 둔다.collectAsLazyPagingItems()로 수집하고, LazyPagingItems를 하위 component에 파라미터로 전달한다.DevicePreview를 쓴다. 기존 코드에는 ComponentPreview·원시 Preview가 혼재하나 신규 코드는 DevicePreview로 통일한다.ComponentPreview를 쓴다.core:designsystem: feature/domain/platform 동작을 모르는 순수 디자인 컴포넌트와 토큰. 예: NekiTheme, top bar, action bar, button, dialog, bottom sheet, modifier, preview helper.core:ui: 앱 전역에서 재사용하지만 기능/도메인/플랫폼 동작이 섞인 UI/Compose 유틸. 예: MviIntentStore, collectWithLifecycle, NekiToast(WindowManager 기반 표시 class — 동명의 순수 composable은 designsystem에 있음), PhotoComponent, SelectDialog, DoubleButtonOptionBottomSheet, loading/selection overlay.component/: 해당 feature 문맥에서만 의미 있는 UI 조각. 예: archive 전용 album/photo item, pose 전용 bottom sheet, auth 약관 content.Use when naming branches, writing commit messages, creating or editing GitHub issues, or creating or editing GitHub pull requests in this repository.
Use when a project decision changes or the codebase drifts from what a skill or agent documents, and this repository's harness (skills, agents, AGENTS.md, discussions.md) needs to be updated to match.
Use after implementing an Android code change, when verifying an existing implementation, or before declaring development complete. Select project skills, run risk-based verification, coordinate Reviewer and QA agents, and repeat only when evidence requires a fix.
Use when adding or changing behavior in an existing feature screen, including MVI State, Intent, Effect, ViewModel reducers, one-shot effects, API result handling, or UI event wiring in this Android repository.
Use when adding a new Compose feature screen with Contract, ViewModel, Route, Screen, Preview, or MVI store in this Android repository.
Use when adding or changing Firebase Analytics events, AnalyticsEvent definitions, AnalyticsLogger calls, screen view logs, click logs, filter logs, or completion logs in this Android repository.