菜单
Use when designing or implementing mobile screen composition, stacks, tabs, modals, sheets, back behavior, deep-linked routes, lists, safe areas, keyboards, or adaptive phone, tablet, foldable, and multi-window layouts.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/blackprince001/skills --skill mobile-design-views-and-navigation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Always-on coding style and organization rules for naming, file shape, comments, types, module boundaries, pattern use, errors, and avoiding unnecessary abstraction across languages and tracks.
Use when setting up or modifying CI pipelines — the quality-gate sequence every change passes, shift-left ordering, feeding failures back to agents, and keeping the pipeline under 10 minutes.
Use when designing any public interface — REST/GraphQL endpoints, module contracts, component props — Hyrum's Law, contract-first, consistent error semantics, validate at boundaries, extend rather than break.
基于 SOC 职业分类
正在显示 SKILL.md
| name | mobile-design-views-and-navigation |
| description | Use when designing or implementing mobile screen composition, stacks, tabs, modals, sheets, back behavior, deep-linked routes, lists, safe areas, keyboards, or adaptive phone, tablet, foldable, and multi-window layouts. |
Apply core UX, design engineering, state/data, accessibility, and performance rules. Navigation is a user-visible state machine: every destination has identity, entry conditions, back behavior, restoration, deep-link behavior, and accessibility focus behavior.
Use stacks for hierarchical drill-down, tabs for persistent peer destinations, sheets/modals for bounded tasks, and full-screen presentation only when the task truly replaces context. Preserve the platform's back gesture/button and provide visible dismissal when gestures are undiscoverable. Avoid nested navigators that create ambiguous ownership or duplicate headers.
Make routes typed and deep-linkable where product value requires it. Validate external link input, handle unauthenticated and missing-resource states, and restore the intended destination after the required gate. Persist only navigation state that remains valid across app versions.
Respect safe areas and system bars without padding every child independently. Keep primary content scrollable when text grows, handle keyboards without hiding the focused field or action, and retain useful state across rotation, resize, backgrounding, and restoration. Prefer native controls and containers for built-in interaction and accessibility.
Use virtualized/recycling lists for unbounded data, stable identities, bounded item work, explicit empty/loading/error/refresh states, predictable pagination, and appropriately sized images. Measure before adding memoization or custom recycling behavior.
Change composition from window/container class and content pressure, not device names. A wider layout may become split-view, multi-column, or inspector-based while preserving task order and route identity. Do not stretch a phone layout across a tablet or assume orientation is fixed.
For Expo Router details, read references/upstream-expo-router/. Native SwiftUI navigation details
live under mobile-setup-platform-standards/references/upstream-swiftui-pro/.
Verify cold launch and restoration, every deep link, back/dismiss behavior, tab/stack state, authentication gates, keyboard, safe areas, large text, screen-reader focus, empty/error/offline states, large lists, rotation, resizing, tablet/foldable layouts, and interrupted transitions.
