菜单
Use when designing, implementing, or reviewing navigation in Compose Multiplatform projects — route modeling, back stack ownership, argument passing, NavOptions, conditional flows, deep links, and adaptive navigation UI.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when reviewing implemented Kotlin Multiplatform / Compose Multiplatform code for architecture consistency, business-logic placement, state correctness, concurrency, Compose quality, design-system usage, security, performance, resilience, and maintainability.
Use when reviewing KMP architecture, feature proposals, PR structure, layer boundaries, state-holder design, Android entry-point discipline, source-set placement, modularization, and long-term maintainability in Kotlin Multiplatform / Compose Multiplatform projects.
Refactor discipline for existing codebases. Enforces scope control, migration safety, compatibility, observability, and tests to keep refactors reviewable and low-risk.
Use when diagnosing and fixing bugs in a Kotlin Multiplatform project. Focus on root-cause analysis, minimal safe fixes, KMP correctness, UI/state/data/persistence/concurrency issues, and regression prevention.
Use when implementing or extending a feature in a Kotlin Multiplatform project. Provides pre-coding inspection, KMP source-set discipline, state pipeline design, architectural defaults, security/performance guardrails, and implementation rules. Forward-looking only — not a review skill.
Use when reviewing or designing Gradle build structure for KMP projects — shared build logic, convention plugins, version catalogs, Android KMP plugin usage, source-set configuration, and module dependency hygiene.
| name | kotlin-navigation-compose-multiplatform |
| description | Use when designing, implementing, or reviewing navigation in Compose Multiplatform projects — route modeling, back stack ownership, argument passing, NavOptions, conditional flows, deep links, and adaptive navigation UI. |
| license | Apache-2.0 |
| metadata | {"author":"Mariano Miani","version":"1.2.0"} |
Use this skill when designing, implementing, or reviewing navigation in a Compose Multiplatform project.
This skill is intentionally strict. Its purpose is to keep route modeling coherent, back stack behavior explicit, argument passing minimal, navigation side effects controlled, and multiplatform routing boundaries clean across Android and shared Compose code.
Navigation library scope: This skill covers Jetpack Navigation 2 and its Compose Multiplatform equivalent — the current stable navigation library. Navigation 3 (Jetpack Navigation 3, a ground-up redesign) was in alpha as of mid-2025 and has a substantially different back-stack model, entry API, and lifecycle integration. If your project uses Navigation 3, verify which guidance applies before proceeding. Navigation 3 status: https://developer.android.com/guide/navigation/navigation3
The navigation design should optimize for:
Do not treat navigation as only “go from screen A to screen B”. Treat it as app-state movement with user-history consequences.
This skill covers Compose Multiplatform Navigation 2 (current stable as of mid-2025), which is the navigation-compose integration used in most KMP projects today.
Jetpack Navigation 3 (a significant redesign with a different back-stack model built around NavDisplay and NavEntry) was in alpha as of mid-2025. If the project is using Navigation 3, some of this guidance — particularly around NavController ownership, popUpTo, and argument passing — applies differently. Verify against current Navigation 3 documentation before applying this skill to a Navigation 3 project.
This skill covers Jetpack Navigation 2 (stable) as used in Compose Multiplatform, including the compose-navigation artifact and the NavHost/NavController model. Navigation 3 (a separate alpha-stage redesign as of mid-2025) uses a fundamentally different back-stack model and is not covered here. If the project uses Navigation 3, verify that the patterns below still apply — some will, some will not. Check the Navigation 3 documentation for current guidance.
Unless the project has a strong reason not to, prefer:
NavController or equivalent navigation stateNavController downwardpopUpTo, inclusive, saveState, restoreState, and launchSingleTopCheck whether routes are modeled clearly and intentionally.
Prefer:
In Compose Multiplatform navigation, a route identifies a destination and defines the arguments required to navigate there, while staying separate from the UI implementation.
Flag as a concern when:
Android explicitly recommends that composables expose navigation events rather than receiving a NavController reference directly.
Check whether:
NavControlleronOpenDetails() rather than calling navigate() directlynavigate() is called from callbacks or controlled side effects, not from normal rendering pathsFlag as a concern when:
NavController is passed deep into leaf composablesnavigate() directlyNavigation state should have a clear owner.
Check whether:
Flag as a concern when:
Android’s Navigation docs treat navigate() and popBackStack() as core app-history operations.
Check whether:
popBackStack() or navigateUp() intentionallypopBackStack() cases are handled safely instead of leaving the app in an invalid stateFlag as a concern when:
Review the explicit use of navigation options.
Important options include:
popUpTo()inclusivesaveStaterestoreStatelaunchSingleTopCheck whether:
popUpTo() is used to shape history intentionallyinclusive is used only when removing the target destination is correctsaveState / restoreState are used where returning to preserved stacks matterslaunchSingleTop is used to avoid duplicate top destinationsFlag as a concern when:
popUpTo() behavior is hard to reason aboutAndroid recommends passing the minimum necessary information and avoiding complex object transfer through navigation arguments.
Check whether:
Flag as a concern when:
Conditional navigation should be modeled through shared state and explicit transitions, not scattered checks.
Check whether:
Flag as a concern when:
Navigation is a side effect and should be coordinated with hoisted state.
Check whether:
Flag as a concern when:
Compose Multiplatform navigation supports destination deep links through NavDeepLink patterns.
Check whether:
Flag as a concern when:
On web, Compose Multiplatform can bind navigation state to browser history and URL fragments.
Check whether:
bindToBrowserNavigation() (this API is part of the Compose Multiplatform web-target navigation layer; verify its current stability status against the Compose Multiplatform release notes before treating it as stable API)@SerialName or custom route mapping is used when default generated URLs are too implementation-heavyFlag as a concern when:
Navigation chrome should adapt to available space.
Check whether:
Flag as a concern when:
Check whether the navigation host and app shell are decomposed clearly.
Prefer:
Flag as a concern when:
Android’s Navigation docs support configuring transitions between destinations, including enter, exit, pop-enter, and pop-exit transitions.
Check whether:
Flag as a concern when:
Check whether each destination remains a meaningful UI boundary.
Prefer:
Flag as a concern when:
Navigation architecture should support validation without relying only on full app runs.
Check whether:
Flag as a concern when:
Likely to cause broken navigation behavior or architectural drift.
Examples:
NavController ownernavigate() called from composable rendering pathsWorkable, but likely to create maintenance cost.
Examples:
Structurally acceptable but worth improving.
Examples:
When performing the review, respond with:
Navigation summary
NavController / back-stack ownershipWhat is structurally sound
Issues by review dimension
NavController ownershipSeverity for each issue
Concrete recommendations
NavControllerlaunchSingleTop / popUpTo / saveStateSuggested target structure
Open risks
Be direct and practical. Do not praise navigation just because it works on one device or one happy path. If the design is weak, say why clearly.
NavController deep into composablesnavigate() during composition