ccc-mobile
Load ONE skill. Get the entire mobile development domain. From cross-platform frameworks to native iOS/Android to distribution and engagement.
Sub-Skills
| # |
Skill |
Command |
Description |
| 1 |
react-native |
/react-native |
React Native development patterns, navigation, native modules |
| 2 |
flutter |
/flutter |
Flutter/Dart development, widget architecture, state management |
| 3 |
swiftui |
/swiftui |
SwiftUI development, MVVM patterns, iOS-specific features |
| 4 |
jetpack-compose |
/jetpack-compose |
Jetpack Compose for Android, Material Design 3 |
| 5 |
mobile-testing |
/mobile-testing |
Mobile testing with Detox, Maestro, XCTest, Espresso |
| 6 |
app-store-optimization |
/app-store-optimization |
ASO for App Store and Play Store listings |
| 7 |
push-notifications |
/push-notifications |
Push notification setup with FCM, APNs, OneSignal |
| 8 |
deep-linking |
/deep-linking |
Universal links, app links, deep linking configuration |
How To Use
Step 1: Tell me what you're building and which platform(s) you're targeting.
Step 2: I'll confirm your framework choice, target OS versions, and any constraints before routing to the specialist.
Step 3: The specialist skill handles the work. You get mobile expertise across the full stack without loading 8 separate skills.
Routing Matrix
| Your Intent |
Route To |
Don't Confuse With |
| "Build a React Native app" / "RN navigation" / "Expo" |
react-native |
flutter (different framework entirely) |
| "Flutter app" / "Dart widget" / "Riverpod" |
flutter |
react-native (JS-based, not Dart) |
| "SwiftUI view" / "iOS native" / "Combine" |
swiftui |
jetpack-compose (Android, not iOS) |
| "Compose UI" / "Android native" / "Material 3" |
jetpack-compose |
swiftui (iOS, not Android) |
| "Test my app" / "E2E mobile test" / "Detox" |
mobile-testing |
Framework skills (building, not testing) |
| "App Store listing" / "Play Store optimization" |
app-store-optimization |
push-notifications (engagement, not discovery) |
| "Push notifications" / "FCM" / "APNs" |
push-notifications |
deep-linking (navigation, not messaging) |
| "Deep links" / "Universal links" / "App links" |
deep-linking |
push-notifications (messaging, not navigation) |
Campaign Templates
Cross-Platform App (React Native)
react-native -> scaffold project, navigation, state managementpush-notifications -> integrate FCM + APNs via React Native Firebasedeep-linking -> configure universal links and app linksmobile-testing -> set up Detox E2E testsapp-store-optimization -> optimize store listings before launch- Deliver: production-ready cross-platform app with notifications, deep linking, and tests
Native iOS App
swiftui -> build UI with SwiftUI, implement MVVM architecturepush-notifications -> configure APNs and notification handlingdeep-linking -> set up universal links and custom URL schemesmobile-testing -> write XCTest unit and UI testsapp-store-optimization -> optimize App Store listing- Deliver: native iOS app with full notification and deep link support
Native Android App
jetpack-compose -> build UI with Compose, Material Design 3push-notifications -> configure FCM and notification channelsdeep-linking -> set up Android App Links and intent filtersmobile-testing -> write Espresso and Compose UI testsapp-store-optimization -> optimize Play Store listing- Deliver: native Android app with Material 3, notifications, and testing
Platform Selection Guide
Which platform should you target?
|
+-- Need iOS + Android from one codebase?
| +-- Team knows React/JS? -> react-native
| +-- Want best cross-platform performance? -> flutter
|
+-- Need native platform experience?
| +-- iOS only? -> swiftui
| +-- Android only? -> jetpack-compose
|
+-- Not sure?
+-- Start with react-native if team knows JS/TS
+-- Start with flutter if team wants maximum UI control
Context Strategy
This CCC domain uses on-demand loading. Sub-skills have disable-model-invocation: true so they only load when explicitly invoked, keeping your context lean.
1---2name: ccc-mobile3description: CCC domain — complete mobile development ecosystem — 8 skills in one. React Native, Flutter, SwiftUI, Jetpack Compose, testing, ASO, push notifications, and deep linking.4---56# ccc-mobile78> Load ONE skill. Get the entire mobile development domain. From cross-platform frameworks to native iOS/Android to distribution and engagement.910## Sub-Skills1112| # | Skill | Command | Description |13|---|-------|---------|-------------|14| 1 | react-native | `/react-native` | React Native development patterns, navigation, native modules |15| 2 | flutter | `/flutter` | Flutter/Dart development, widget architecture, state management |16| 3 | swiftui | `/swiftui` | SwiftUI development, MVVM patterns, iOS-specific features |17| 4 | jetpack-compose | `/jetpack-compose` | Jetpack Compose for Android, Material Design 3 |18| 5 | mobile-testing | `/mobile-testing` | Mobile testing with Detox, Maestro, XCTest, Espresso |19| 6 | app-store-optimization | `/app-store-optimization` | ASO for App Store and Play Store listings |20| 7 | push-notifications | `/push-notifications` | Push notification setup with FCM, APNs, OneSignal |21| 8 | deep-linking | `/deep-linking` | Universal links, app links, deep linking configuration |2223## How To Use2425**Step 1:** Tell me what you're building and which platform(s) you're targeting.2627**Step 2:** I'll confirm your framework choice, target OS versions, and any constraints before routing to the specialist.2829**Step 3:** The specialist skill handles the work. You get mobile expertise across the full stack without loading 8 separate skills.3031## Routing Matrix3233| Your Intent | Route To | Don't Confuse With |34|-------------|----------|--------------------|35| "Build a React Native app" / "RN navigation" / "Expo" | `react-native` | `flutter` (different framework entirely) |36| "Flutter app" / "Dart widget" / "Riverpod" | `flutter` | `react-native` (JS-based, not Dart) |37| "SwiftUI view" / "iOS native" / "Combine" | `swiftui` | `jetpack-compose` (Android, not iOS) |38| "Compose UI" / "Android native" / "Material 3" | `jetpack-compose` | `swiftui` (iOS, not Android) |39| "Test my app" / "E2E mobile test" / "Detox" | `mobile-testing` | Framework skills (building, not testing) |40| "App Store listing" / "Play Store optimization" | `app-store-optimization` | `push-notifications` (engagement, not discovery) |41| "Push notifications" / "FCM" / "APNs" | `push-notifications` | `deep-linking` (navigation, not messaging) |42| "Deep links" / "Universal links" / "App links" | `deep-linking` | `push-notifications` (messaging, not navigation) |4344## Campaign Templates4546### Cross-Platform App (React Native)471. `react-native` -> scaffold project, navigation, state management482. `push-notifications` -> integrate FCM + APNs via React Native Firebase493. `deep-linking` -> configure universal links and app links504. `mobile-testing` -> set up Detox E2E tests515. `app-store-optimization` -> optimize store listings before launch526. Deliver: production-ready cross-platform app with notifications, deep linking, and tests5354### Native iOS App551. `swiftui` -> build UI with SwiftUI, implement MVVM architecture562. `push-notifications` -> configure APNs and notification handling573. `deep-linking` -> set up universal links and custom URL schemes584. `mobile-testing` -> write XCTest unit and UI tests595. `app-store-optimization` -> optimize App Store listing606. Deliver: native iOS app with full notification and deep link support6162### Native Android App631. `jetpack-compose` -> build UI with Compose, Material Design 3642. `push-notifications` -> configure FCM and notification channels653. `deep-linking` -> set up Android App Links and intent filters664. `mobile-testing` -> write Espresso and Compose UI tests675. `app-store-optimization` -> optimize Play Store listing686. Deliver: native Android app with Material 3, notifications, and testing6970## Platform Selection Guide7172```73Which platform should you target?74|75+-- Need iOS + Android from one codebase?76| +-- Team knows React/JS? -> react-native77| +-- Want best cross-platform performance? -> flutter78|79+-- Need native platform experience?80| +-- iOS only? -> swiftui81| +-- Android only? -> jetpack-compose82|83+-- Not sure?84 +-- Start with react-native if team knows JS/TS85 +-- Start with flutter if team wants maximum UI control86```8788## Context Strategy8990This CCC domain uses on-demand loading. Sub-skills have `disable-model-invocation: true` so they only load when explicitly invoked, keeping your context lean.
KevinZai