Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

mobile-apps-create

/mobile-apps-create

Prowadzi przez budowę natywnych aplikacji mobilnych Salesforce na iOS i Androida: Mobile SDK, logowanie, SmartStore i agenta Agentforce.

Repozytorium
sf-skills ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
23.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
4
Przestarzałość

Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Prowadzi przez budowę natywnych aplikacji mobilnych Salesforce na iOS i Androida: Mobile SDK, logowanie, SmartStore i agenta Agentforce.

Wyzwalacze z opisu

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\
Oryginalny opis (EN)

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 non-Salesforce mobile app, using React Native / Flutter / Ionic without Salesforce integr

Jak działa

  1. Before routing
  2. Routing — which SDK family?
  3. Routing — which platform?
  4. Combined workflows (Mobile SDK + Agentforce SDK)
  5. Loading a child skill
Sekcje z nagłówków SKILL.md, w oryginale · 64 linii, 638 słów
Podgląd SKILL.md
---
name: mobile-apps-create
description: "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 non-Salesforce mobile app, using React Native / Flutter / Ionic without Salesforce integration, asking about generic mobile UI design, or working on a Salesforce-adjacent web/desktop surface (LWC, Experience Cloud, Mobile Publisher branding-only)."
metadata:
  version: "1.0"
  domains: ["Mobile"]
  cliTools:
    - tool: ["npx"]
      semver: ">=9.0.0"
---

# Salesforce Mobile

Route the user to the right SDK-family skill for building Salesforce-connected mobile apps. Do not implement features here; child skills own scenario detection and step-by-step instructions.

## Before routing

Disambiguate on two dimensions: **SDK family** (Mobile SDK vs. Agentforce SDK) and **platform** (iOS vs. Android). They are not mutually exclusive — an app can use both SDKs.

If the user's intent could plausibly map to either SDK, ask before routing. Guessing wrong wastes the user's time because the child skills are platform- and SDK-specific.

## Routing — which SDK family?

| User's situation | SDK |
|---|---|
| Authenticating end users to Salesforce, syncing records (MobileSync), storing data offline (SmartStore), biometric login, push notifications, REST integration | **Mobile SDK** |
| Embedding an Agentforce agent — chat UI, agent conversations, conversational features as the primary surface | **Agentforce SDK** |
| Both (data-driven app with an embedded agent) | **Mobile SDK first**, then **Agentforce SDK** layered on top |

### Tiebreakers when both seem to apply

- Is the agent the *primary surface* (chat-first app), or a *feature inside* an otherwise data-driven app?
  - Primary → Agentforce SDK
  - Feature → Mobile SDK; embed the agent via Agentforce SDK alongside it
- Are end users authenticating into Salesforce data?
  - Yes → Mobile SDK is required (Agentforce SDK can be added on top).
  - No → Agentforce SDK alone is likely sufficient (it uses guest auth).
- Asking about offline storage, sync, REST, push, or biometrics? → Mobile SDK.
- Asking about agent conversations, chat UI, or streaming responses? → Agentforce SDK.

When still unclear, ask the user directly.

## Routing — which platform?

| Platform | Mobile SDK skill | Agentforce SDK skill |
|---|---|---|
| iOS (Swift) | `ios-mobile-sdk` | `integrate-agentforce-ios` |
| Android (Kotlin) | `android-mobile-sdk` | `integrate-agentforce-android` |

If the user wants both platforms, route to each child skill separately — they are independent.

## Combined workflows (Mobile SDK + Agentforce SDK)

When an app needs both:

1. Route to the Mobile SDK platform skill first to scaffold and authenticate.
2. Then you **MUST** load the Agentforce SDK platform skill (`integrate-agentforce-ios` or `integrate-agentforce-android`) to layer the agent surface. Do not hand-write the Agentforce integration — the SDK's dependencies, products, and APIs are not guessable and hand-rolled code will not compile.
3. Treat each child skill's instructions as authoritative for its SDK; do not merge their steps. Each SDK owns its own auth setup, dependency installation order, and initialization sequence — interleaving them produces conflicting config and broken init order.

This sequencing is the only multi-skill logic this skill owns. Everything else lives inside the child skills.

## Loading a child skill

Invoke the child skill by name through the harness. If it is not available locally, prompt the user to install it with `npx skills add <repo>`. If the user confirms (or has pre-authorized installs), run the command and load the child skill — do not make the user go figure out how to continue the workflow. If the user declines, stop and explain that the child skill owns the SDK's setup steps and the workflow cannot continue without it. Each child skill is published from a public repo:

| Skill | Repo | Install command |
|---|---|---|
| `ios-mobile-sdk` | [`forcedotcom/SalesforceMobileSDK-Templates`](https://github.com/forcedotcom/SalesforceMobileSDK-Templates) → `skills/ios-mobile-sdk/` | `npx --yes skills add forcedotcom/SalesforceMobileSDK-Templates --skill ios-mobile-sdk --yes` |
| `android-mobile-sdk` | [`forcedotcom/SalesforceMobileSDK-Templates`](https://github.com/forcedotcom/SalesforceMobileSDK-Templates) → `skills/android-mobile-sdk/` | `npx --yes skills add forcedotcom/SalesforceMobileSDK-Templates --skill android-mobile-sdk --yes` |
| `integrate-agentforce-ios` | [`salesforce/AgentforceMobileSDK-iOS`](https://github.com/salesforce/AgentforceMobileSDK-iOS) → `skills/integrate-agentforce-ios/` | `npx --yes skills add salesforce/AgentforceMobileSDK-iOS --skill integrate-agentforce-ios --yes` |
| `integrate-agentforce-android` | [`salesforce/AgentforceMobileSDK-Android`](https://github.com/salesforce/AgentforceMobileSDK-Android) → `skills/integrate-agentforce-android/` | `npx --yes skills add salesforce/AgentforceMobileSDK-Android --skill integrate-agentforce-android --yes` |

After install, load the child skill and let it take over. Do not inline the child skill's content — the child skill owns scenario detection, prerequisites, and step-by-step instructions.

Wersje

W bazie nie ma innych skilli o nazwie mobile-apps-create.

Identyczna treść występuje jeszcze w 7 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.

Migawka bazy z 13.11.2026 · wersja paczki e61920316502 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100mobile-dev
    Wspiera tworzenie aplikacji mobilnych na iOS, Androida i React Native: budowa aplikacji i ekranów, debugowanie buildów iOS oraz optymalizacja wydajności Androida.
  • 100senior-mobile
    Wspiera tworzenie aplikacji mobilnych na iOS (Swift, SwiftUI), Android (Kotlin, Compose), React Native i Flutter: scaffolding, nawigacja Expo Router, offline-first, wydajność i publikacja w App Store.
  • 85mobile-engineering
    Projektuje, wdraża i przegląda aplikacje mobilne Flutter, React Native, iOS i Android, z trybem offline, wydajnością i publikacją w sklepach.
  • 90mobile-apps
    Wspiera kod w repozytorium aidd dotyczący aplikacji na iOS, Androida, React Native, Flutter, App Store i Google Play.
  • 91create-mobile-app
    Zakłada nową aplikację mobilną Power Apps od zera w Expo, React Native i TypeScript, na iOS i Androida.
  • 100testing-mobile-apps
    Przeprowadza testy aplikacji mobilnych na urządzeniach i symulatorach iOS oraz Android.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.