skills.rest
augustoheiss
augustoheissCOMMUNITY
Explore all skills by this author →
GitHub

agency-salesforce-architect

Design scalable Salesforce architectures with governor-limit budgeting and integration patterns.

Updated Feb 11, 2026
Search Tags:#devops#architecture#integration#ci-cd#data-modeling#salesforce#governor-limits
One-click install
npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-salesforce-architect-augustoheiss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-salesforce-architect
Source: https://github.com/augustoheiss/LogicDefense/tree/main/.gemini/skills/agency-salesforce-architect
Command: npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-salesforce-architect-augustoheiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of designing and governing Salesforce architectures that must scale to enterprise volumes while avoiding governor limit exceptions, fragile automations, and brittle integrations that cause data loss or outages.

Core Features & Use Cases

  • Org Assessment & Roadmapping: Map objects, automations, integrations, and technical debt to produce a prioritized remediation and roadmap.
  • Integration & Failure Handling Patterns: Recommend sync vs async approaches, retries, circuit breakers, and dead-letter queues for reliable cross-system communication.
  • Data Model & Governance: Provide data model reviews, record type and sharing strategies, external ID designs for integrations, and PII handling guidance.
  • Deployment & CI/CD Strategy: Advise on source-tracking, scratch orgs, Salesforce DX, DevOps Center, and ADRs to document trade-offs and governor impact.
  • Use Case: Convert a risky single-org implementation with hundreds of flows and triggers into a governable architecture with ADRs, bulkified automation strategies, and a CI/CD pipeline.

Quick Start

Assess my Salesforce org with its current object counts, automation inventory, and integration endpoints and produce an Architecture Decision Record recommending a single-org or multi-org strategy, a governor-limit budget, prioritized remediation steps, and the integration pattern for each external system.

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 that scales without hitting governor limits?▼

Designing a scalable Salesforce architecture requires budgeting governor limits upfront, applying bulkified automation patterns, and selecting reliable retryable integration patterns. This approach maps technical debt and object inventories into a governable enterprise roadmap.

What is the best way to handle high-volume Salesforce integrations without data loss?▼

The best way to handle high-volume Salesforce integrations involves implementing asynchronous patterns with retries, circuit breakers, and dead-letter queues. This ensures reliable cross-system communication and prevents outages during complex enterprise data synchronization.

How do I assess technical debt in a Salesforce org with hundreds of flows and triggers?▼

Assessing Salesforce org technical debt involves mapping current object counts, automation inventory, and integration endpoints. This produces a prioritized remediation roadmap and an Architecture Decision Record recommending single-org or multi-org deployment strategies.

Does my enterprise Salesforce deployment need a CI/CD pipeline using Salesforce DX?▼

Enterprise Salesforce deployments require a CI/CD pipeline using Salesforce DX or DevOps Center to manage source-tracking and scratch orgs. This deployment strategy documents trade-offs and governor impacts through Architecture Decision Records.

When should I use single-org versus multi-org strategy for complex Salesforce automations?▼

A single-org strategy suits consolidated enterprise deployments, while a multi-org strategy isolates complex automations and high data volumes. Documenting this choice in an Architecture Decision Record clarifies governor-limit budgets and integration reliability trade-offs.

How do I govern data models and PII handling in a multi-cloud Salesforce deployment?▼

Governing multi-cloud Salesforce data models requires reviewing record types, sharing strategies, and external ID designs for integrations. Providing explicit PII handling guidance ensures data model governance across enterprise deployments facing high data volumes.

Related Skills

Explore More Software Engineering Skills→
raykuonzraykuonz
4

graphify-sf

Parse local Salesforce SFDX directories and map metadata relationships with provenance tags.

Community
Advanced
tomztomz

sf-cli

Automates Salesforce DX workflows via the sf CLI for authentication, deployments, and metadata operations.

Community
Advanced
Marwan78888Marwan78888
16

salesforce-developer

Automate Salesforce development workflows across Apex, Lightning Web Components, and DX pipelines.

Community
Advanced
pauljbernardpauljbernard
5

Data Architecture Excellence

Guide enterprise data strategy, governance, modeling, integration, and analytics architecture.

Community
Advanced