菜单
Reviews watchOS code for app lifecycle, complications (ClockKit/WidgetKit), WatchConnectivity, and performance constraints. Use when reviewing code with import WatchKit, WKExtension, WKApplicationDelegate, WCSession, or watchOS-specific patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implement, review, and refactor SQLDelight code in this repo. Use for `.sq` or `.sqm` files, `TetrisLiteDatabase`, `SqlDriver`, `SqlSchema<QueryResult.AsyncValue<Unit>>`, `ColumnAdapter`, `DatabaseManager`, `DatabaseDriverFactory`, DAO/query changes, migrations, coroutines query flows, or SQLDelight KMP Gradle wiring.
Implement, review, and refactor Metro DI in this repo. Use for @DependencyGraph, createGraph/createGraphFactory, AppScope, BindingContainer, ContributesTo, Binds, Provides, SingleIn, platform app graphs, Metro aggregation, or Metro plugin wiring in Kotlin/KMP modules.
Write, review, and refactor MVIKotlin code in this repo. Use when the task mentions MVIKotlin, StoreFactory, Store<Intent, State, Label>, CoroutineExecutor, Reducer, Bootstrapper, Labels, MviView, LoggingStoreFactory, TimeTravelStoreFactory, or when implementing a feature store/component wired through Decompose.
This skill should be used when the user is creating or modifying a Decompose component, mentions "ComponentContext", "retainedInstance", "stateKeeper", "instanceKeeper", "InstanceKeeper", "MutableValue", "Value<", component lifecycle, state preservation, instance retaining, back button handling in a component, or when writing a class that implements or extends a Decompose component interface. Also applies when the user asks how to structure a component, how to keep state across config changes, how to implement a ViewModel equivalent with Decompose, or how to handle the back button in a component.
This skill should be used when the user is integrating Decompose with Jetpack or Multiplatform Compose UI, mentions "subscribeAsState", the "Children" composable from Decompose, "stackAnimation", "predictiveBackAnimation", "ChildPages" composable, "ChildPanels" composable, rendering a ChildSlot in Compose, tab navigation with a bottom bar using Decompose, "LifecycleController" for desktop, Compose previews for Decompose components, or back handling in Compose using Decompose's BackHandler.
This skill should be used when the user is implementing navigation with Decompose, mentions "ChildStack", "ChildSlot", "ChildPages", "ChildPanels", "ChildItems", "StackNavigation", "SlotNavigation", "PagesNavigation", "PanelsNavigation", "childStack", "childSlot", "childPages", "childPanels", asks which navigation model to use, asks about push/pop navigation, dialog navigation, pager navigation, tab navigation, master-detail layout, deep linking with Decompose, navigation configuration classes, or "bringToFront".
| name | watchos-code-review |
| description | Reviews watchOS code for app lifecycle, complications (ClockKit/WidgetKit), WatchConnectivity, and performance constraints. Use when reviewing code with import WatchKit, WKExtension, WKApplicationDelegate, WCSession, or watchOS-specific patterns. |
| Issue Type | Reference |
|---|---|
| App lifecycle, scenes, background modes, extended runtime | references/lifecycle.md |
| ClockKit, WidgetKit, timeline providers, Smart Stack | references/complications.md |
| WCSession, message passing, file transfer, reachability | references/connectivity.md |
| Memory limits, background refresh, battery optimization | references/performance.md |
@WKApplicationDelegateAdaptor for lifecycle eventsscenePhase read from root view (not sheets/modals where it's always .active)WKExtendedRuntimeSession started only while app is active (not from background)applicationDidFinishLaunching (not just delegate)URLSessionDownloadTask (not DataTask) used for background network requestsTimelineEntryRelevance implemented for Smart Stack prioritizationactivate(); singleton pattern usedisReachable checked before sendMessage; transferUserInfo for critical datasetTaskCompletedWithSnapshot)?isLuminanceReduced is true?TabView nested within another TabView? (Memory leak on watchOS)