agency-salesforce-architect

Automate Salesforce architecture design and governance for enterprise multi-cloud environments.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jay6697117/agency-agents-antigravity --skill agency-salesforce-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-salesforce-architect
Source: https://github.com/jay6697117/agency-agents-antigravity/tree/main/.agents/skills/agency-salesforce-architect
Command: npx skills add https://github.com/jay6697117/agency-agents-antigravity --skill agency-salesforce-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Salesforce architecture for enterprise-scale orgs requires governance, multi-cloud design, and standardized deployment strategies to prevent debt, outages, and integration bottlenecks.

Core Features & Use Cases

  • Multi-cloud architecture planning for Sales, Service, Marketing, and Data Cloud with a single source of truth.
  • Enterprise integration patterns including REST, CDC, Platform Events, and CI/CD integration.
  • Data model governance, governor-limit-aware design, and deployment strategy optimized for large data volumes.
  • AppExchange ISV architecture support and org strategy (single vs multi-org) for scalable deployments.
  • Use Case: Migrating a 200-object Salesforce org with 47 active automations to a governance-driven architecture.

Quick Start

Provide an enterprise-level Salesforce architecture blueprint and validate it against governor limits and bulkification requirements.

Frequently Asked Questions about agency-salesforce-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a Salesforce architecture blueprint that prevents governor limit issues?

Design a Salesforce architecture blueprint using governor-limit-aware design and bulkification requirements to validate enterprise-scale data handling. This prevents outages and ensures your architecture can process large data volumes efficiently without hitting platform limits.

What is the best way to plan multi-cloud Salesforce architecture across Sales, Service, and Data Cloud?

Plan multi-cloud Salesforce architecture by establishing a single source of truth across Sales, Service, Marketing, and Data Cloud. This approach standardizes integration patterns and data model governance, preventing technical debt and integration bottlenecks across enterprise deployments.

How do I migrate a large Salesforce org with hundreds of objects and active automations to a governance-driven architecture?

Migrate a large Salesforce org by applying a governance-driven architecture strategy to hundreds of objects and active automations. This involves validating deployment strategies, standardizing data models, and applying declarative-first approaches to ensure scalable, secure data handling.

Which enterprise integration patterns should I use for Salesforce data synchronization and deployment?

Use enterprise integration patterns like REST, Change Data Capture (CDC), and Platform Events for Salesforce data synchronization. Pair these with a CI/CD integration strategy to standardize deployments and prevent integration bottlenecks across large data volumes.

Does a declarative-first approach work for enterprise Salesforce org strategy and large data volumes?

A declarative-first approach works for enterprise Salesforce org strategy by prioritizing standard platform features before custom code. When combined with governor-limit-aware design and bulkification, it effectively scales for large data volumes while maintaining secure data handling.

When should I choose a single-org versus multi-org strategy for scalable Salesforce deployments?

Choose a single-org or multi-org strategy for scalable Salesforce deployments based on your enterprise architecture needs for data isolation and governance. Evaluating org strategy prevents integration bottlenecks and ensures standardized deployment across complex multi-cloud environments.