菜单
Add a Navigation 3 destination — a route key, a per-screen route function, and one line in the host. Use when asked to "add a screen to navigation", "add a destination", "wire a screen into the nav graph", or "navigate to X".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add a screen's composables to a feature module using the Route → Screen → Content structure. Use when asked to "add a screen", "build the <X> screen", "wire up a screen's UI", or to render a feature's state. Pairs with add-viewmodel.
Add a ViewModel to a feature module using the Action / State / Event triad, depending on use case / repository interfaces. Use when asked to "add a viewmodel" or to wire a screen's state, actions, and events. The screen's composables are a separate skill (add-screen).
Add a reusable design-system Composable to the :ui module — stateless, themed via RickAndMortyTheme tokens, with a preview. Use when asked to "add a button", "add a shared component", "add a card/loader/empty state", or to build any reusable UI primitive shared across screens.
Unit-test a use case with hand-written fake repositories. Use when asked to "test a use case", "add use case tests", or to verify a use case's aggregation and error-propagation logic.
Unit-test a ViewModel's Action → State → Event behaviour with fakes. Use when asked to "test a viewmodel", "add viewmodel tests", or to verify a screen's state transitions and one-time events.
Add a repository to :data:core as composable single-unit repositories ([Verb][Name]Repository) encapsulated by a parent contract, each mapping a data source's RemoteResult into DataResult. Use when asked to "add a repository", "wire up a repository", or to expose data-layer operations to domain/presentation.
| name | add-destination |
| description | Add a Navigation 3 destination — a route key, a per-screen route function, and one line in the host. Use when asked to "add a screen to navigation", "add a destination", "wire a screen into the nav graph", or "navigate to X". |
This project uses Navigation 3. Navigation lives in the app's navigation
package; each screen is one NavKey route + one xxxRoute() function called
from the host (MainNavDisplay). Adding a destination is three small edits.
navigation/routes/Route.kt — a sealed Route : NavKey
where each destination is @Serializable (a data object for no-arg screens,
a data class for screens with arguments).navigation/routes/<Screen>Route.kt: an
EntryProviderScope<NavKey> extension that registers entry<Route.X> { } and
wires the feature's public <Feature>Route composable. It takes the
NavBackStack<NavKey> so its callbacks can push/pop. One function per screen
keeps each destination's navigation concerns in one place.navigation/MainNavDisplay.kt — its entryProvider just calls
each xxxRoute(backStack). Navigate by backStack.add(Route.X); go back with
backStack.removeLastOrNull() (the host's onBack).<Feature>Route plain callback lambdas (see
add-viewmodel). Only the app knows the graph.navigation/routes/Route.kt:
sealed interface Route : NavKey {
@Serializable data object Characters : Route
@Serializable data class CharacterDetail(val id: Int) : Route // args → data class
}
navigation/routes/<Screen>Route.kt. Takes the back stack; wires the feature's
public composable with navigation callbacks:
fun EntryProviderScope<NavKey>.charactersRoute(
backStack: NavBackStack<NavKey>,
) {
entry<Route.Characters> {
CharactersRoute(
onCharacterClick = { id -> backStack.add(Route.CharacterDetail(id)) },
)
}
}
navigation/MainNavDisplay.kt — one call inside entryProvider:
entryProvider<NavKey> {
charactersRoute(backStack)
// characterDetailRoute(backStack) // each new screen = one more line
}
The back stack itself is created once by the host's caller (e.g. MainActivity)
via rememberNavBackStack(Route.Characters) and passed into MainNavDisplay.
./gradlew :app:compileDebugSources --console=plain
(Set JAVA_HOME to a JDK 21 — e.g. an SDKMAN *-jbr — if the shell can't find
Java.)
@Serializable and in Route : NavKey (data object no-arg,
data class with args).xxxRoute(backStack) registers entry<Route.X> and wires the feature's
<Feature>Route with navigation-callback lambdas.xxxRoute(backStack) line added to MainNavDisplay's entryProvider.:app:compileDebugSources succeeds.