mobile-apps-create
The entry point for building any Salesforce native mobile app on iOS or Android. TRIGGER when the user says: "build a Salesforce iOS app", "add Salesforce login to my Android app", "set up Mobile SDK", "add MobileSync / SmartStore offline storage", "embed an Agentforce agent in my mobile app", "add Agentforce chat to iOS/Android", or otherwise asks to create, extend, or integrate a Salesforce mobile experience in Swift or Kotlin (MSDK, Agentforce SDK, or both). SKIP when the user is building a n
Security Assessment
About mobile-apps-create
This skill is the entry point and router for building any Salesforce-connected native mobile app on iOS or Android. It solves the problem of choosing the correct SDK-family skill for a given mobile task rather than implementing features itself. It disambiguates along two dimensions — SDK family (Salesforce Mobile SDK versus Agentforce SDK) and platform (iOS/Swift versus Android/Kotlin) — and routes to the appropriate child skill, which owns the actual scenario detection and step-by-step instructions.
It provides decision tables and tiebreakers to make the routing call: Mobile SDK for authenticating end users, syncing records with MobileSync, offline storage with SmartStore, biometric login, push notifications, and REST integration; Agentforce SDK when embedding an agent chat UI as the primary conversational surface (which can use guest auth). When an app needs both, it prescribes a specific sequence — scaffold and authenticate with the Mobile SDK platform skill first, then layer the Agentforce SDK on top — while treating each child skill's instructions as authoritative and not merging their steps, since each SDK owns its own auth, dependency order, and initialization. It maps each of the four child skills (ios-mobile-sdk, android-mobile-sdk, integrate-agentforce-ios, integrate-agentforce-android) to its public GitHub repo and an npx skills add install command, and instructs the assistant to install and load the child skill when it is not available locally.
The target users are mobile developers building Salesforce native apps in Swift or Kotlin. It explicitly excludes non-Salesforce apps, React Native/Flutter/Ionic without Salesforce integration, generic mobile UI design, and Salesforce-adjacent web surfaces like LWC or Experience Cloud.
FAQ
Does this skill build the app itself?
No. It is a router. It decides which SDK-family and platform child skill to load and then hands off; the child skills own scenario detection, prerequisites, and step-by-step implementation.
How does it choose between Mobile SDK and Agentforce SDK?
Mobile SDK for user authentication, MobileSync record syncing, SmartStore offline storage, biometrics, push, and REST. Agentforce SDK when an embedded agent chat is the primary surface. If both apply, it uses tiebreakers and, when still unclear, asks the user.
What if my app needs both SDKs?
Route to the Mobile SDK platform skill first to scaffold and authenticate, then layer the Agentforce SDK on top. The steps of the two child skills must not be merged, since each SDK owns its own auth, dependency order, and initialization.
What if the required child skill isn't installed?
The skill prompts to install it with an npx skills add command pointing at the child skill's public repo (for example forcedotcom/SalesforceMobileSDK-Templates or salesforce/AgentforceMobileSDK-iOS/Android), then loads it. If the user declines, the workflow stops because the child skill owns the setup steps.
When should I not use this skill?
For non-Salesforce mobile apps, React Native/Flutter/Ionic without Salesforce integration, generic mobile UI design questions, or Salesforce-adjacent web/desktop surfaces such as LWC, Experience Cloud, or branding-only Mobile Publisher.
Install mobile-apps-create
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
forcedotcom/sf-skills