Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mobile-engineering
Decide native vs React Native vs Flutter by the app's real needs (platform-specific UX, performance, OS-feature access, team), and set the offline-first sync strategy (local source of truth, write queue, conflict resolution) and lifecycle-survival plan.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mobile-engineering:mobile-platform-choiceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Need | Approach |
| Need | Approach |
|---|---|
| Heavy platform-specific UX / top performance / newest OS features | Native (Swift+Kotlin) |
| Largely shared business app, one team, faster shared iteration | React Native / Flutter |
Name the trade; don't default to preference.
Local DB = source of truth, synced to server; a write queue for offline mutations; a conflict-resolution policy (last-write-wins / merge / prompt). Retrofitting offline is a rewrite.
Survive backgrounding, process death, restoration. The OS will kill you; plan for it.
npx claudepluginhub mcorbett51090/ravenclaude --plugin mobile-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.