iOS (Swift, SwiftUI), Android (Kotlin, Compose), cross-platform (Flutter, React Native), and game development (Unity, Unreal).
Provides mobile and game development guidance for iOS (Swift/SwiftUI), Android (Kotlin/Compose), cross-platform (Flutter/React Native), and engines (Unity/Unreal). Claude uses this when users ask about building mobile apps or games, choosing platforms, or following learning paths.
/plugin marketplace add pluginagentmarketplace/custom-plugin-cloudflare/plugin install custom-plugin-cloudflare@pluginagentmarketplace-cloudflareThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/mobile_config.yamlreferences/MOBILE_GUIDE.mdscripts/pwa_validator.py| Platform | Language | Framework | Timeline | Job Market |
|---|---|---|---|---|
| iOS | Swift | SwiftUI | 6-9 mo | High |
| Android | Kotlin | Compose | 6-9 mo | High |
| Cross-Platform | Dart | Flutter | 4-6 mo | Growing |
| Games | C# | Unity | 12-24 mo | Moderate |
[1] Swift Fundamentals (4-6 wk)
│ └─ Types, optionals, closures, protocols
│
▼
[2] SwiftUI (4-6 wk)
│ └─ Views, modifiers, state, binding
│
▼
[3] Navigation + Data (3-4 wk)
│ └─ NavigationStack, SwiftData/Core Data
│
▼
[4] Networking + Async (2-3 wk)
│ └─ URLSession, async/await, Combine
│
▼
[5] Testing + App Store (2 wk)
└─ XCTest, TestFlight, submission
2025 Stack: Swift 5.10 + SwiftUI + SwiftData + Xcode 16
[1] Kotlin Fundamentals (4-6 wk)
│ └─ Null safety, coroutines, data classes
│
▼
[2] Jetpack Compose (4-6 wk)
│ └─ Composables, state, effects
│
▼
[3] Architecture (3-4 wk)
│ └─ MVVM, Room, Navigation
│
▼
[4] Networking + DI (2-3 wk)
│ └─ Retrofit, Hilt, Flow
│
▼
[5] Testing + Play Store (2 wk)
└─ JUnit, Espresso, release
2025 Stack: Kotlin 2.0 + Jetpack Compose + Room + Hilt
[1] Dart Fundamentals (2-3 wk)
│
▼
[2] Flutter Widgets (3-4 wk)
│
▼
[3] State Management (2-3 wk)
│ └─ Riverpod or Bloc
│
▼
[4] Backend Integration (2 wk)
│ └─ Firebase, REST APIs
│
▼
[5] Deploy to Both Stores (1 wk)
2025 Stack: Flutter 3.x + Dart 3.x + Riverpod + Firebase
[1] Game Basics (4-6 wk)
│ └─ Game loop, input handling
│
▼
[2] Unity/C# Fundamentals (6-8 wk)
│ └─ GameObjects, Components, Scripts
│
▼
[3] Physics + Graphics (4-6 wk)
│ └─ Rigidbody, colliders, shaders
│
▼
[4] Audio + Polish (2-4 wk)
│
▼
[5] Publish (ongoing)
└─ Steam, App Store, Play Store
2025 Stack: Unity 6 LTS + C# OR Unreal 5.4 + C++
Which platform?
│
├─► Apple ecosystem only?
│ └─► iOS (Swift + SwiftUI)
│
├─► Android ecosystem only?
│ └─► Android (Kotlin + Compose)
│
├─► Both platforms?
│ ├─► Performance-critical? → Native for both
│ ├─► Budget/time limited? → Flutter
│ └─► Web developer background? → React Native
│
└─► Making games?
├─► 2D/3D indie → Unity
├─► AAA quality → Unreal
└─► Simple 2D → Godot
| Engine | Market | Language | Learning | Best For |
|---|---|---|---|---|
| Unity | 51% | C# | Medium | Indie, mobile, VR |
| Unreal | 31% | C++/BP | Hard | AAA, high-fidelity |
| Godot | 10% | GDScript | Easy | Indie, 2D |
Native vs Cross-platform?
├─► Need platform-specific APIs (HealthKit, ARCore)? → Native
├─► Performance-critical (AR/VR, complex animations)? → Native
├─► Budget or time limited? → Flutter
├─► Team knows JavaScript? → React Native
└─► Starting from scratch? → Flutter (best DX)
Simulator works, device doesn't?
├─► Missing entitlements/capabilities?
├─► Different iOS/Android version?
├─► Network connectivity issues?
└─► Always test on real devices from day 1
App rejected by store?
├─► Read rejection reason carefully
├─► Check App Store Review Guidelines
├─► Most common: metadata issues, crashes, spam
└─► Appeal if unjustified
| Symptom | Root Cause | Recovery |
|---|---|---|
| Slow UI | Too many recompositions | Profile, optimize state |
| Memory leaks | Not cleaning up resources | Use lifecycle-aware components |
| App rejected | Guidelines violation | Read guidelines BEFORE building |
| Game stutters | Draw call overhead | Object pooling, LOD, batching |
Specify your target platform for a detailed learning plan.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.