Salesforce Architect

Designs Salesforce multi-cloud architectures with integration patterns, governor limit budgets, and data model governance.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill salesforce-architect-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Salesforce Architect
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/specialized/salesforce-architect
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill salesforce-architect-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Enterprise Salesforce orgs accumulate technical debt through poorly designed data models, unbulkified triggers, and integrations that fail silently. This Skill provides senior-level solution architecture guidance that accounts for governor limits, deployment strategy, and long-term maintainability from the start. ## Core Features & Use Cases - Architecture Decision Records: Produces structured ADRs documenting context, alternatives, governor limit impact, and consequences for each significant design decision. - Integration Pattern Design: Selects and diagrams sync/async integration approaches (REST, Platform Events, CDC, MuleSoft) with retry logic, circuit breakers, and dead letter queues. - Governor Limit Budgeting: Quantifies SOQL, DML, CPU, and heap consumption per transaction so designs stay within platform limits before implementation begins. - Use Case: When planning a Salesforce-to-ERP integration for an org with 200 custom objects, use this Skill to produce an integration pattern diagram, a data model review checklist, and an ADR comparing middleware options with their governor limit trade-offs. ## Quick Start Ask the Salesforce Architect to review your org's data model and design an integration pattern for connecting Salesforce to your external ERP system.

Frequently Asked Questions about Salesforce Architect

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

FAQPage Schema
How do I design a Salesforce integration pattern that handles failures?▼

Every Salesforce callout needs retry logic with exponential backoff, circuit breakers, and a dead letter queue such as a custom error object. The Skill produces integration diagrams specifying auth method, payload format, rate limits, and batch sizes for each external system.

When should I use Platform Events vs Change Data Capture in Salesforce?▼

Platform Events support custom payloads and decouple producers from consumers, making them preferred for cross-system business events. CDC mirrors sObject fields with field-level change tracking, suiting data synchronization use cases tied to object transaction volume.

How do I avoid hitting Salesforce governor limits in triggers?▼

Bulkify all trigger logic to handle 200 records, delegate to handler classes with one trigger per object, and budget against the 100 SOQL and 150 DML synchronous limits. The Skill provides a governor limit budget template to quantify headroom per transaction.

Should I use Flow or Apex for Salesforce automation?▼

Use declarative tools like Flows, formula fields, and validation rules first, but switch to Apex when branching becomes complex or bulkification is required. The Skill helps identify when declarative automation becomes unmaintainable and documents the decision in an ADR.

What are the limitations of changing a Salesforce data model after go-live?▼

Changing the data model after go-live is roughly ten times more expensive than getting it right initially. Master-detail versus lookup decisions, sharing model design, and large data volume strategies like skinny tables must be documented before building anything.