From mobile-engineering
Build React Native/Flutter well: maximize shared logic while honoring per-platform conventions, manage the bridge/platform-channel native boundary (and write native modules when needed), avoid framework-specific performance pitfalls, and handle push/deep-links/offline once with secrets in the secure store.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mobile-engineering:cross-platform-mobileThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Share logic/UI; honor **per-platform** navigation, conventions, accessibility. Identically non-native on both = UX fail.
Share logic/UI; honor per-platform navigation, conventions, accessibility. Identically non-native on both = UX fail.
RN bridge / Flutter platform channels: batch crossings; write native modules for unavailable capabilities. Don't fight the framework for the last 5%.
RN: FlatList virtualization, Fabric/TurboModules, avoid bridge chatter. Flutter: const widgets, avoid rebuilds. Profile.
Push + deep/universal links + offline in the shared layer. Secrets -> secure store plugin (Keychain/Keystore), never AsyncStorage in clear.
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.