cloud-specific-deployment-architecture
Deployment architecture quirks per Salesforce cloud: Industries (OmniStudio), Marketing Cloud (MC packages), Commerce Cloud, Data Cloud, Agentforce. What ships via metadata API, what ships via cloud-specific tools, ordering, dependencies. NOT for generic DevOps (use devops skills). NOT for cross-cloud data flow (use cross-cloud-data-deployment).
Best use case
cloud-specific-deployment-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deployment architecture quirks per Salesforce cloud: Industries (OmniStudio), Marketing Cloud (MC packages), Commerce Cloud, Data Cloud, Agentforce. What ships via metadata API, what ships via cloud-specific tools, ordering, dependencies. NOT for generic DevOps (use devops skills). NOT for cross-cloud data flow (use cross-cloud-data-deployment).
Teams using cloud-specific-deployment-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cloud-specific-deployment-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cloud-specific-deployment-architecture Compares
| Feature / Agent | cloud-specific-deployment-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deployment architecture quirks per Salesforce cloud: Industries (OmniStudio), Marketing Cloud (MC packages), Commerce Cloud, Data Cloud, Agentforce. What ships via metadata API, what ships via cloud-specific tools, ordering, dependencies. NOT for generic DevOps (use devops skills). NOT for cross-cloud data flow (use cross-cloud-data-deployment).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Cloud-Specific Deployment Architecture Activate when planning deployments that include non-core components: OmniStudio (FlexCards, Integration Procedures, DataRaptors), Marketing Cloud packages, Commerce Cloud sites, Data Cloud Data Streams and DMOs, Agentforce agents, Industries Data Kit. Each cloud has quirks in what the metadata API covers and what needs cloud-specific tools. ## Before Starting - **Inventory the component types per cloud.** Metadata API covers most of Platform + Sales/Service; OmniStudio, Marketing Cloud, Commerce Cloud, Data Cloud each have their own piece of the puzzle. - **Understand dependency direction.** Permission sets reference objects; OmniScripts reference Integration Procedures; Agentforce Topics reference Actions. Deploy dependencies first. - **Decide the tool per cloud.** One tool rarely covers all. Combine: SFDX for platform, MC DevTools for Marketing Cloud, B2C Commerce CLI for Commerce Cloud, Data Cloud Migration Tool for Data Cloud. ## Core Concepts ### OmniStudio deployment OmniStudio components (FlexCards, OmniScripts, Integration Procedures, DataRaptors, Expression Sets) deploy via the OmniStudio Migration Tool or via SFDX with the Industries Data Kit. Ordering matters: DataRaptors before Integration Procedures before OmniScripts before FlexCards. ### Marketing Cloud deployment Marketing Cloud is a separate stack. Email templates, journeys, automations, data extensions — handled via MC DevTools (Accenture/Salesforce community-maintained), MC REST API, or enterprise tools like Copado MC. Metadata API does NOT cover Marketing Cloud content. ### Commerce Cloud (B2C / B2B) deployment B2C: Storefront cartridges via SFCC Studio + Business Manager + Build API. B2B: Experience Cloud site + Commerce Cloud metadata via SFDX. Shared services (catalogs, price books) need coordinated deploys. ### Data Cloud deployment Data Streams, DMOs, Calculated Insights, Activations: partial metadata-API coverage improving by release. Data Cloud Migration Tool + JSON definitions cover the rest. Identity resolution rules deploy separately. ### Agentforce deployment Agents, topics, actions, prompt templates ship via metadata API as of late 2025 / early 2026. Guardrails and Einstein Trust Layer settings are org-scoped. Cross-org test must re-run after every topic/action change. ## Common Patterns ### Pattern: Hybrid pipeline per cloud, single orchestrator Orchestrator (Copado, Gearset, custom Jenkins) calls per-cloud tools: SFDX for platform, MC DevTools for Marketing Cloud, OmniStudio Migration Tool for Industries. One PR can carry all but deploys branch by cloud with ordering. ### Pattern: Data Kit as the Industries distribution unit For Industries customers, the Industries Data Kit bundles OmniStudio + SObjects + data mappings. Deploying a Data Kit is the unit of change for many Industries components. ### Pattern: Agentforce topic + action atomic unit A topic and the actions it calls deploy together. Separating them breaks agent routing. Package them as a single deployable change set or pipeline stage. ## Decision Guidance | Cloud / Component | Primary Tool | Secondary | |---|---|---| | Platform (Apex, LWC, Flow) | SFDX / Metadata API | Copado, Gearset, Flosum | | OmniStudio | OmniStudio Migration Tool + SFDX | Industries Data Kit | | Marketing Cloud | MC DevTools + MC API | Copado MC | | Commerce Cloud B2C | SFCC Studio + Build API | Salesforce CLI plugins | | Data Cloud | Data Cloud Migration Tool | Metadata API (partial) | | Agentforce | Metadata API | Agentforce management console | ## Recommended Workflow 1. Inventory the components by cloud and classify by deploy mechanism. 2. Draw the per-cloud deploy pipeline and mark ordering dependencies. 3. Pick tooling per cloud with one orchestrator coordinating stage gates. 4. Build a dependency graph across clouds (e.g., OmniScript → Platform Apex class). 5. Validate on a pilot sandbox; measure deploy time per stage. 6. Document rollback per cloud; note that some clouds (Marketing, Commerce) do not support "rollback" natively and require replay. 7. Instrument pipeline with health checks per cloud; failures alert to owner teams. ## Review Checklist - [ ] Component inventory per cloud complete - [ ] Tool selected per cloud with rationale - [ ] Ordering dependencies documented in a diagram - [ ] Pilot deployment validated end-to-end - [ ] Rollback strategy per cloud documented - [ ] Secrets and connected app credentials stored securely - [ ] Pipeline health dashboard live ## Salesforce-Specific Gotchas 1. **OmniStudio export is JSON; ordering matters.** Loading OmniScripts before their Integration Procedures breaks references silently. 2. **Marketing Cloud data extensions include schema and data.** Deploying a DE over an existing one with a schema drift deletes the drift fields. 3. **Data Cloud DMO activation flags are environment-scoped.** A DMO deployed from sandbox to prod may be inactive until manually activated. ## Output Artifacts | Artifact | Description | |---|---| | Per-cloud component inventory | What exists, in which cloud | | Tool map | Tool chosen per cloud with rationale | | Dependency graph | Cross-cloud ordering | | Rollback playbook per cloud | Replay vs revert per cloud | ## Related Skills - `architect/deployment-automation-architecture` — orchestration layer - `architect/cross-cloud-data-deployment` — data flow between clouds - `devops/cicd-pipeline-design` — platform CI/CD
Related Skills
salesforce-shield-deployment
Roll out Shield (Platform Encryption + Event Monitoring + Field Audit Trail) end-to-end, sequencing feature enablement to avoid data lockout. NOT for Classic Encryption or general PE design.
experience-cloud-security
Use when configuring access controls, sharing, or site security for authenticated or guest Experience Cloud (community) users: external OWD, Sharing Sets, Share Groups, CSP, clickjack protection, guest user record access. NOT for internal sharing model configuration (use sharing-and-visibility).
omnistudio-deployment-datapacks
Use when exporting, importing, or version-controlling OmniStudio components using DataPacks via the OmniStudio DataPacks tool or vlocity CLI. Covers DataPack export/import, Git version control integration, CI/CD for OmniStudio. NOT for SFDX-based metadata deployment of non-OmniStudio components.
headless-experience-cloud
Use when building custom frontends (React, Vue, mobile, static sites) that consume Salesforce CMS content via the Connect REST API headless delivery endpoint. Triggers: 'headless Salesforce CMS', 'deliver CMS content to external frontend', 'React app Salesforce content API', 'custom frontend Experience Cloud data', 'CMS delivery channel API'. NOT for standard Experience Builder site development. NOT for CMS Connect (3rd-party CMS federation into Experience Builder). NOT for Experience Cloud LWC components rendered inside a site.
experience-cloud-search-customization
Use this skill when configuring or extending search on an Experience Cloud site — covering Search Manager scope configuration, LWR vs Aura search component selection, federated search setup, guest user search access, and custom search result components. NOT for SOSL/SOQL query development. NOT for internal Salesforce global search or Einstein Search for agents.
experience-cloud-multi-idp-sso
Use this skill when configuring multiple identity providers (OIDC and/or SAML) on a single Experience Cloud site or across tenant-specific portals in the same org — covering auth provider registration, Start SSO URL routing, Federation ID mapping, RegistrationHandler implementation, and simultaneous SP+IdP topology. Trigger keywords: multiple identity providers Experience Cloud, multi-tenant SSO community portal, vendor and citizen portal same site, OIDC SAML both on login page, tenant-specific login routing community. NOT for internal Salesforce employee SSO configuration. NOT for single auth provider setups — see experience-cloud-authentication for basic SSO.
experience-cloud-lwc-components
Use when building custom LWC components for Experience Cloud (Experience Builder sites, LWR portals, Aura-based communities). Covers community context imports, guest user Apex access patterns, navigation API differences between LWR and Aura, and JS-meta.xml target configuration for Experience Builder exposure. NOT for internal LWC components deployed to Lightning App Builder or standard record pages (see lwc/lwc-development). NOT for Aura community components. Trigger keywords: build LWC for Experience Cloud, custom component community portal LWC, guest user LWC component, community context import salesforce, lightningCommunity target, @salesforce/community, guest Apex.
experience-cloud-authentication
Use when building custom login pages, social SSO flows, self-registration flows, or passwordless OTP login for Experience Cloud (community) sites. Trigger keywords: custom login page Experience Cloud, social SSO community portal, passwordless login Experience Cloud, self-registration custom flow, headless authentication community, auth provider OIDC SAML site. NOT for internal SSO configuration (use identity/sso skills). NOT for standard username/password authentication with no customization.
experience-cloud-api-access
Use this skill when configuring or troubleshooting API access for Experience Cloud external users and guest users: guest user Apex data access, Customer Community Plus or Partner Community REST/SOAP API access, external user OAuth scopes, and sharing enforcement on API responses. Trigger keywords: Experience Cloud API access external user, community user REST API, guest user API limits, Customer Community API permissions, external user OAuth. NOT for internal Salesforce API authentication, non-community OAuth flows, or internal user API security.
net-zero-cloud-setup
Use this skill when configuring Salesforce Net Zero Cloud — including Scope 1/2/3 emission source modeling via the StnryAssetCrbnFtprnt / VehicleAssetCrbnFtprnt / Scope3CrbnFtprnt object families, emission factor library setup (EmssnFctr / EmssnFctrSet), DPE-driven carbon calculation jobs, supplier engagement scoring, and CSRD / ESRS / TCFD disclosure pack mapping. Triggers on: Net Zero Cloud setup, Sustainability Cloud carbon accounting, Scope 1 2 3 emissions Salesforce, emission factor library, supplier engagement Net Zero, ESG disclosure pack mapping. NOT for ESG content scoring (use Marketing Cloud), NOT for general financial reporting (use Accounting Subledger), NOT for energy-only utility billing (use Energy & Utilities Cloud).
manufacturing-cloud-setup
Use this skill when configuring Salesforce Manufacturing Cloud — including Sales Agreement setup, Account-Based Forecasting (ABF) recalc jobs, run-rate management, Rebate Management programs, channel inventory tracking via Channel Revenue Management, and Group Membership / OrderItem-to-SalesAgreement reconciliation. Triggers on: Manufacturing Cloud setup, Sales Agreement Salesforce, account-based forecast recalculation, run rate manufacturing, rebate program setup, channel revenue management. NOT for general Sales Cloud opportunity-to-order flow (use standard Opportunity / Order), NOT for Field Service install-base management (use FSL skills), NOT for Automotive Cloud dealer modeling (use automotive-cloud-setup).
data-cloud-zero-copy-federation
Use this skill when configuring or troubleshooting Data Cloud Zero Copy / Lakehouse Federation against Snowflake, Databricks, BigQuery, or Redshift — including external Data Lake Object setup, query semantics through federation, refresh and cache behavior, and choosing federation versus physical ingestion. Triggers on: Data Cloud federated DLO setup, query latency against external warehouse, Snowflake/Databricks/BigQuery integration with Data Cloud, federation vs ingestion decision. NOT for physical Ingestion API streaming/bulk patterns (use data-cloud-integration-strategy), not for CRM Analytics external connectors (use analytics-external-data), not for outbound Data Cloud activation to external systems (use data-cloud-activation-development).