菜单
Use when implementing mobile offline behavior, local persistence and sync, permissions, background work, notifications, deep links, app clips, native modules, battery-sensitive work, device storage, or interrupted lifecycle behavior.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/blackprince001/skills --skill mobile-build-device-realities命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | mobile-build-device-realities |
| description | Use when implementing mobile offline behavior, local persistence and sync, permissions, background work, notifications, deep links, app clips, native modules, battery-sensitive work, device storage, or interrupted lifecycle behavior. |
Apply core state/data, security, performance, APIs/contracts, and accessibility first. Assume networks disappear, processes die, permissions change, storage fills, clocks shift, notifications arrive late, and the app resumes with stale state.
Classify every important task as offline-capable, read-only stale, queued, or unavailable with a clear explanation. Persist durable commands before presenting them as queued; attach identity, idempotency, ordering, expiry, retry, conflict, and dead-letter behavior. Reconcile on foreground and connectivity return without duplicating effects.
Persist the minimum state needed for restoration and validate/migrate it on launch. Treat app backgrounding or process death as possible after any await. Save user work incrementally and keep server authority, device cache, secure credentials, and ephemeral UI state distinct.
Ask for permission only when the user invokes a feature that needs it, explain value before the system prompt where useful, and handle deny, restricted, provisional, one-time, and later-revoked states. Provide a settings route only when it helps recovery. The app's core experience should not require unrelated permissions.
Minimize background tasks, location, sensors, wakeups, network transfer, and polling. Use platform schedulers and push/event triggers, declare constraints, make work resumable/idempotent, and expose last successful sync where freshness matters.
Notifications require meaningful opt-in, user-controlled categories/quiet behavior, minimal sensitive lock-screen content, stable deep links, and server-side authorization when opened. Do not use notification permission as an onboarding gate.
Validate universal/app links, custom schemes, deferred links, shortcuts, widgets, and App Clips as untrusted routes. Define behavior for signed-out users, missing content, expired campaigns, and unsupported app versions.
references/upstream-expo-data-fetching/.references/upstream-expo-module/.references/upstream-expo-app-clip/.Test airplane mode, slow/flapping networks, duplicate delivery, process death, background/foreground, permission denial/revocation, storage pressure, clock change, notification states, every link entry, version migration, battery-sensitive work, conflict recovery, and account/tenant isolation.