forcedotcom/sf-skills

mobile-apps-create

The entry point for building any Salesforce native mobile app on iOS or Android.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/forcedotcom/sf-skills --skill mobile-apps-create

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

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 situationSDK
Authenticating end users to Salesforce, syncing records (MobileSync), storing data offline (SmartStore), biometric login, push notifications, REST integrationMobile SDK
Embedding an Agentforce agent — chat UI, agent conversations, conversational features as the primary surfaceAgentforce 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?

PlatformMobile SDK skillAgentforce SDK skill
iOS (Swift)ios-mobile-sdkintegrate-agentforce-ios
Android (Kotlin)android-mobile-sdkintegrate-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. Route to the Agentforce SDK platform skill to layer the agent surface.
  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:

SkillRepoInstall command
ios-mobile-sdk`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` → skills/android-mobile-sdk/npx --yes skills add forcedotcom/SalesforceMobileSDK-Templates --skill android-mobile-sdk --yes
integrate-agentforce-ios`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` → 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.

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
forcedotcom
Społeczność

design-systems-slds-apply

Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\".

Instalacje / 1h
1
GitHub Stars
1,2 tys.
Aktualizacja
13 lis
forcedotcom
Społeczność

dx-code-analyzer-run

Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulner

Instalacje / 1h
1
GitHub Stars
1,2 tys.
Aktualizacja
13 lis
forcedotcom
Społeczność

experience-lwc-accessibility-jest-run

Use ALWAYS when running Sa11y accessibility Jest tests for an LWC — locally before pushing, producing the command(s), running one file vs a suite, selecting tests by naming convention, saving Sa11y-rendered HTML, or reproducing a Sa11y/A11yBug failure. Covers core (Bazel; bazel test // : ) and standalone npx jest (.accessibility.test.js, @sa11y/jest). REQUIRED for a run-plan.md, a failing a11y test's exit code, or SA11Y/A11yBug/core-Bazel test paths. DO NOT TRIGGER for functional Jest tests, a11

Instalacje / 1h
1
GitHub Stars
1,2 tys.
Aktualizacja
13 lis
forcedotcom
Społeczność

experience-lwc-generate

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc//.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use platform-apex-generate), Aura components, or Visualforce.

Instalacje / 1h
1
GitHub Stars
1,2 tys.
Aktualizacja
13 lis