mobile-engineering
v0.3.4Mobile-engineering team — agents (mobile-architect, ios-engineer, android-engineer, cross-platform-engineer) for native and cross-platform mobile apps: the native-vs-React-Native-vs-Flutter decision, iOS craft (Swift/SwiftUI, the app lifecycle, concurrency), Android craft (Kotlin/Jetpack Compose, lifecycle, coroutines), and the cross-cutting mobile concerns (offline-first + sync, secure on-device storage, push notifications/deep links, battery/network constraints, and the App Store / Play Store release pipeline + review). skills, a decision-tree knowledge bank (platform-choice + offline-sync trees + a dated 2026 capability map), best-practices, templates, commands, an advisory hook. Seams: shared web patterns -> frontend-engineering, the backend API -> api-engineering/backend-engineering, auth -> auth-identity, CI/CD signing -> devops-cicd. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install mobile-engineering for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install mobile-engineering@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/mobile-engineering/.
Plugin files
├── .claude-plugin/plugin.json├── skills/android-craft/SKILL.md├── skills/app-store-release-pipeline/SKILL.md├── skills/cross-platform-mobile/SKILL.md├── skills/ios-craft/SKILL.md└── skills/mobile-platform-choice/SKILL.md
Included Skills5
Build native Android the platform way: state-driven Jetpack Compose (state hoisting, remember, list keys), coroutines/Flow with lifecycle-scoped structured concurrency, Keystore/EncryptedSharedPreferences, WorkManager background respecting Doze, and Material + accessibility.
Step-by-step guide for automating the iOS App Store and Google Play release pipeline — code signing, build automation with Fastlane, TestFlight and internal track distribution, phased rollout, and the common pipeline failure modes.
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.
Build native iOS the platform way: state-driven SwiftUI with correct property-wrapper ownership, Swift Concurrency (async/await, actors, @MainActor), Keychain secure storage, lifecycle/background-task handling, and Human Interface Guidelines + accessibility.
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.
Plugin manifests1
{
"name": "mobile-engineering",
"version": "0.3.4",
"description": "Mobile-engineering team — agents (mobile-architect, ios-engineer, android-engineer, cross-platform-engineer) for native and cross-platform mobile apps: the native-vs-React-Native-vs-Flutter decision, iOS craft (Swift/SwiftUI, the app lifecycle, concurrency), Android craft (Kotlin/Jetpack Compose, lifecycle, coroutines), and the cross-cutting mobile concerns (offline-first + sync, secure on-device storage, push notifications/deep links, battery/network constraints, and the App Store / Play Store release pipeline + review). skills, a decision-tree knowledge bank (platform-choice + offline-sync trees + a dated 2026 capability map), best-practices, templates, commands, an advisory hook. Seams: shared web patterns -> frontend-engineering, the backend API -> api-engineering/backend-engineering, auth -> auth-identity, CI/CD signing -> devops-cicd. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"mobile",
"ios",
"android",
"swift",
"swiftui",
"kotlin",
"jetpack-compose",
"react-native",
"flutter",
"offline-first",
"push-notifications",
"deep-links",
"app-store",
"play-store",
"mobile-ci"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
},
"lspServers": "./.lsp.json"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[mobile-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/mobile-engineering)