反应本机移动强化

工程开发 社区

技能解读

当前原文的自动摘译,尚未人工审校。

何时使用

当任务提到以下任何想法时使用:React Native 测试或 Expo 验证移动回归检查 iOS 或 Android 安全区域、导航、手势、键盘或底部扩展坞问题深度链接、QR 流、恢复门或错误工作空间/错误用户恢复

重点领域

始终首先测试这些风险领域: 受保护的内容安全 恢复、重新身份验证、工作区切换、深层链接或 QR 条目缓存期间不会出现过时的任务刷新 当工作区、主题或会话不再匹配时 离线真实性

程序

首先运行存储库支持的验证集。 pnpm --filter @kanban-lite/mobile run lint pnpm --filter @kanban-lite/mobile run doctor pnpm --filter @kanban-lite/mobile run start -- --offline --clear --port 8088 cd packages/mobile && APP_VARIANT=development pnpm exec expo config --json

强化检查表

在调用更改完成之前使用此快速通道:恢复门永远不会过早显示受保护的内容深度链接和 QR 路线在任务详细信息安装安全区域和底部操作坞之前验证工作区和会话 iOS 和 Android 上的离线同步状态明确且真实

避免

避免这些释放枪:将 lint 成功视为足够的移动验证仅在线测试快乐路径假设浏览器身份验证行为直接映射到 Expo 将拒绝或不匹配错误隐藏在缓存内容后面

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
工程开发
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@tomevault-io · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# React Native Mobile Hardening

Use this skill when the goal is to **test, harden, and de-risk** Kanban Lite mobile changes before they surprise users in the field. Small bugs become big bugs once a worker is offline, gloved up, and standing in the rain.

## When to Use

Use when the task mentions any of these ideas:

- React Native testing or Expo validation
- mobile regression checks for iOS or Android
- safe area, navigation, gesture, keyboard, or bottom-dock issues
- deep links, QR flows, restore gate, or wrong-workspace/wrong-user recovery
- offline sync, pending resend, conflict review, or stale-cache bugs
- camera, attachment capture, upload states, or QR scanning
- performance, startup time, jank, list scrolling, or render churn
- release hardening, preview builds, EAS profiles, or app identity checks

## Focus Areas

Always test these risk areas first:

1. **Protected-content safety**
   - no stale task flash during restore, reauth, workspace switch, deep links, or QR entry
   - cache purge behavior when workspace, subject, or session no longer match

2. **Offline truthfulness**
   - explicit resend for comments, forms, checklist intents, and attachment drafts
   - no silent replay of unsafe server mutations
   - clear `Pending`, `Needs connection`, and conflict states

3. **Field-worker ergonomics**
   - safe area clearance
   - large touch targets
   - one obvious primary action in the thumb zone
   - outdoor-readable contrast and short recovery copy

4. **Cross-platform correctness**
   - iOS and Android navigation behavior
   - deep links and scheme handling
   - keyboard overlap, gesture interactions, and back behavior

## Procedure

1. **Run the repo-supported validation set first.**
   - `pnpm --filter @kanban-lite/mobile run lint`
   - `pnpm --filter @kanban-lite/mobile run doctor`
   - `pnpm --filter @kanban-lite/mobile run start -- --offline --clear --port 8088`
   - `cd packages/mobile && APP_VARIANT=development pnpm exec expo config --json`
   - `cd packages/mobile && APP_VARIANT=preview pnpm exec expo config --json`

2. **Walk the highest-risk product flows.**
   - cold start and restore gate
   - `My Work` and `Due`
   - task detail
   - deep-link open
   - QR open
   - account/logout/recovery

3. **Exercise every mutation state, not just the happy path.**
   - comments: create, edit, delete, pending, resend
   - attachments: take photo, scan document, choose file, discard draft, remove synced attachment
   - forms: edit, save draft, submit, validation error
   - checklist: show, add, edit, delete, check, uncheck, conflict review
   - named actions: allowed online, denied, and offline-disabled

4. **Check capability and visibility behavior.**
   - hidden task means no task UI, not a disabled shell
   - denied mutation capability means hidden control, not a teasing disabled button
   - allowed-but-offline means either explicit local draft or a clear disabled state

5. **Profile the mobile experience for friction.**
   - look for unnecessary re-renders, long list jank, layout jumps, and oversized media work
   - verify the sticky action dock does not fight the keyboard or safe area
   - check that loading and sync states are calm instead of noisy or duplicated
   - prefer simple, stable interactions before adding fancy transitions

6. **Re-check release and app identity assumptions.**
   - `app.config.ts` and `eas.json` must agree on variant handling
   - preview and development identifiers should remain coexistence-safe
   - release changes should not assume production readiness beyond the current staged contract

7. **Document any failure by class, not just by symptom.**
   - safety issue: stale flash, wrong-workspace content, auth leakage
   - offline issue: pending state lies, silent replay, missing resend review
   - platform issue: iOS only, Android only, keyboard/gesture/back behavior
   - performance issue: slow startup, scroll jank, heavy image flow, repeated renders

## Hardening Checklist

Use this quick pass before calling a change done:

- restore gate never shows protected content too early
- deep links and QR routes validate workspace and session before task detail mounts
- safe area and bottom action dock work on iOS and Android
- offline sync states are explicit and truthful
- camera and attachment flows preserve durable local drafts when needed
- checklist, forms, comments, and actions respect capability gates
- preview/development config still resolves cleanly from Expo config

## Avoid

Avoid these release-footguns:

- treating lint success as sufficient mobile validation
- testing only online happy paths
- assuming browser auth behavior maps directly to Expo
- hiding a denial or mismatch bug behind cached content
- queuing destructive offline actions without explicit user review
- changing release profiles without re-checking variant-specific identifiers

## Done When

The mobile change is hardened when:

- correctness, offline behavior, and protected-content safety were all exercised
- iOS and Android interaction details were checked intentionally
- performance regressions were considered, not merely hoped away
- Expo validation and variant config still align with the repo contract
- release confidence comes from verified flows, not vibes

---
> Source: [borgius/kanban-lite](https://github.com/borgius/kanban-lite) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。